Connect with us

Startups

Fulton Financial (FULT) Q4 Earnings Meet Estimates

Published

on

This story originally appeared on Zacks

Fulton Financial (FULT) came out with quarterly earnings of $0.37 per share, in line with the Zacks Consensus Estimate. This compares to earnings of $0.30 per share a year ago. These figures are adjusted for non-recurring items.

– Zacks

A quarter ago, it was expected that this financial holding company would post earnings of $0.33 per share when it actually produced earnings of $0.45, delivering a surprise of 36.36%.

Over the last four quarters, the company has surpassed consensus EPS estimates three times.

Fulton Financial, which belongs to the Zacks Banks – Northeast industry, posted revenues of $232.68 million for the quarter ended December 2021, surpassing the Zacks Consensus Estimate by 3.14%. This compares to year-ago revenues of $220.15 million. The company has topped consensus revenue estimates three times over the last four quarters.

The sustainability of the stock’s immediate price movement based on the recently-released numbers and future earnings expectations will mostly depend on management’s commentary on the earnings call.

Fulton Financial shares have added about 11.1% since the beginning of the year versus the S&P 500’s decline of -2.2%.

What’s Next for Fulton Financial?

While Fulton Financial has outperformed the market so far this year, the question that comes to investors’ minds is: what’s next for the stock?

There are no easy answers to this key question, but one reliable measure that can help investors address this is the company’s earnings outlook. Not only does this include current consensus earnings expectations for the coming quarter(s), but also how these expectations have changed lately.

Empirical research shows a strong correlation between near-term stock movements and trends in earnings estimate revisions. Investors can track such revisions by themselves or rely on a tried-and-tested rating tool like the Zacks Rank, which has an impressive track record of harnessing the power of earnings estimate revisions.

Ahead of this earnings release, the estimate revisions trend for Fulton Financial: favorable. While the magnitude and direction of estimate revisions could change following the company’s just-released earnings report, the current status translates into a Zacks Rank #2 (Buy) for the stock. So, the shares are expected to outperform the market in the near future. You can see the complete list of today’s Zacks #1 Rank (Strong Buy) stocks here.

It will be interesting to see how estimates for the coming quarters and current fiscal year change in the days ahead. The current consensus EPS estimate is $0.31 on $216.9 million in revenues for the coming quarter and $1.32 on $881.47 million in revenues for the current fiscal year.

Investors should be mindful of the fact that the outlook for the industry can have a material impact on the performance of the stock as well. In terms of the Zacks Industry Rank, Banks – Northeast is currently in the top 15% of the 250 plus Zacks industries. Our research shows that the top 50% of the Zacks-ranked industries outperform the bottom 50% by a factor of more than 2 to 1.

Another stock from the same industry, Bank OZK (OZK), has yet to report results for the quarter ended December 2021. The results are expected to be released on January 20.

This bank is expected to post quarterly earnings of $0.98 per share in its upcoming report, which represents a year-over-year change of +5.4%. The consensus EPS estimate for the quarter has been revised 0.2% lower over the last 30 days to the current level.

Bank OZK’s revenues are expected to be $273 million, up 2.5% from the year-ago quarter.

Just Released: Zacks Top 10 Stocks for 2022

In addition to the investment ideas discussed above, would you like to know about our 10 top picks for the entirety of 2022?

From inception in 2012 through 2021, the Zacks Top 10 Stocks portfolios gained an impressive +1,001.2% versus the S&P 500’s +348.7%. Now our Director of Research has combed through 4,000 companies covered by the Zacks Rank and has handpicked the best 10 tickers to buy and hold. Don’t miss your chance to get in…because the sooner you do, the more upside you stand to grab.

See Stocks Now >>

Want the latest recommendations from Zacks Investment Research? Today, you can download 7 Best Stocks for the Next 30 Days. Click to get this free report
 
Fulton Financial Corporation (FULT): Free Stock Analysis Report
 
Bank OZK (OZK): Free Stock Analysis Report
 
To read this article on Zacks.com click here.
 
Zacks Investment Research

Startups

The FTC files suit to block Microsoft’s Activision Blizzard acquisition

Published

on

The Federal Trade Commission is suing to block the proposed acquisition of Activision Blizzard by Microsoft. It contends that the acquisition, if completed, would give Microsoft an unfair advantage over its competitors.

This morning, the four-person commission voted to issue the lawsuit. The three Democrat members (chair Lina Khan, Rebecca Slaughter and Alvaro Bedoya) voted in favor and the Republican (Christine Wilson) voted against. The commission allegedly met with Microsoft the day prior to discuss concessions, according to a report from The Washington Post.

If its news release is anything to go by, the commissioners weren’t convinced that Microsoft wouldn’t withhold Activision Blizzard’s popular games from competing services. The FTC cited Microsoft’s acquisition of Zenimax, and how games such as Starfield and Redfall became exclusive following its close.

Holly Vedova, director of the FTC’s Bureau of Competition, said in a statement, “Microsoft has already shown that it can and will withhold content from its gaming rivals. Today we seek to stop Microsoft from gaining control over a leading independent game studio and using it to harm competition in multiple dynamic and fast-growing gaming markets.”

Event

GamesBeat Summit: Into the Metaverse 3

Join the GamesBeat community online, February 1-2, to examine the findings and emerging trends within the metaverse.


Register Here

The FTC is not the only government body to express concern about the implications of the acquisition. The UK’s Competition and Markets Authority is currently investigating. It recently closed Phase One of the investigation, and expressed concerns in its issues statement.

The history of the planned acquisition

Microsoft announced its intention to acquire the publisher in January. Through this acquisition, it would become the regent of popular gaming franchises such as Call of Duty, Candy Crush, World of Warcraft and many others. Reportedly, it offered around $69 billion for Activision Blizzard.

The concerns about the scale of the acquisition emerged almost as soon as it was announced. The FTC reportedly moved to investigate the deal almost immediately. Niko Partners senior analyst Daniel Ahmad said at the time that Microsoft would have to pay Activision $3 billion if the deal was blocked.

The current focal point of the antitrust concerns is the Call of Duty franchise. Sony has repeatedly contended, in public statements primarily aimed at the CMA’s investigation, that Microsoft could undermine its competition via these popular and lucrative games. It could, according to Sony, either outright stop publishing them on Sony’s platforms, or it could offer them on its Xbox Game Pass subscription service. Sony claims Call of Duty on Game Pass would diminish demand for Sony consoles even if Call of Duty is still published on them.

Microsoft has, in turn, responded that its competitors have plenty of exclusive titles of their own. It’s also offered to sign 10-year deals with Sony, Nintendo and Valve (the company behind PC games store Steam) to offer Call of Duty titles on their platforms. It announced earlier this week that it has inked such a deal with Nintendo.

Brad Smith, Microsoft’s vice chair and president, said in a statement to The Verge, “We continue to believe that this deal will expand competition and create more opportunities for gamers and game developers. We have been committed since Day One to addressing competition concerns, including by offering earlier this week proposed concessions to the FTC. While we believed in giving peace a chance, we have complete confidence in our case and welcome the opportunity to present our case in court.”



Source link

Continue Reading

Startups

Airtable chief revenue officer, chief people officer and chief product officer are out • TechCrunch

Published

on

As part of Airtable’s decision to cut 20% of staff, or 254 employees, three executives are “parting ways” with the company as well, a spokesperson confirmed over email. The chief revenue officer, chief people officer and chief product officer are no longer with the company.

Airtable’s chief revenue officer, Seth Shaw, joined in November 2020 just one month before Airtable’s chief producer officer Peter Deng came on board. Airtable’s chief people officer, Johanna Jackman, joined Airtable in May 2021 with an ambitious goal to double the company’s headcount to 1,000 in 12 months. The three executives are departing today as a mutual decision with Airtable, but will advise the company through the next phase of transition, the company says. All three executives were reached out to for further comment and this story will be updated with their responses if given.

An Airtable spokesperson declined to comment on if the executives were offered severance pay. The positions will be succeeded by internal employees, introduced at an all-hands meeting to be held this Friday.

Executive departures at this scale are rare, even if the overall company is going through a heavy round of cuts. But CEO and founder Howie Liu emphasized, in an email sent to staff but seen by TechCrunch, that the decision – Airtable’s first-ever lay off in its decade-long history – was made following Airtable’s choice to pivot to a more “narrowly focused mode of execution.”

In the email, Liu described Airtable’s goal – first unveiled in October – to capture enterprise clients with connected apps. Now, instead of the bottom-up adoption that first fueled Airtable’s rise, the company wants to be more focused in this new direction. Liu’s e-mail indicates that the startup will devote a majority of its resources toward “landing and expanding large enterprise companies with at least 1k FTEs – where our connected apps vision will deliver the most differentiated value.”

The lean mindset comes after Airtable reduced spend in marketing media, real estate, business technology and infrastructure, the e-mail indicates. “In trying to do too many things at once, we have grown our organization at a breakneck pace over the past few years. We will continue to emphasize growth, but do so by investing heavily in the levers that yield the highest growth relative to their cost,” Liu wrote.

Airtable seems to be emphasizing that its reduced spend doesn’t come with less ambition, or ability to execute. A spokesperson added over e-mail that all of Airtable’s funds from its $735 million Series F are “still intact.” They also said that the startup’s enterprise side, which makes up the majority of Airtable’s revenue, is growing more than 100% year over year; the product move today just doubles down on that exact cohort.

Current and former Airtable employees can reach out to Natasha Mascarenhas on Signal, a secure encrypted messaging app, at 925 271 0912. You can also DM her on Twitter, @nmasc_. 



Source link

Continue Reading

Startups

Kubernetes Gateway API reality check: Ingress controller is still needed

Published

on

No doubt the new Kubernetes excitement is the Gateway API. One of the more significant changes in the Kubernetes project, the Gateway API is sorely needed. More granular and robust control over Kubernetes service networking better addresses the growing number of use cases and roles within the cloud-native paradigm.

Shared architecture — at all scales — requires flexible, scalable and extensible means to manage, observe and secure that infrastructure. The Gateway API is designed for those tasks. Once fully matured, it will help developers, SREs, platform teams, architects and CTOs by making Kubernetes infrastructure tooling and governance more modular and less bespoke.

But let’s be sure the hype does not get ahead of today’s needs.

The past and future Kubernetes gateway API

There remains a gap between present and future states of Ingress control in Kubernetes. This has led to a common misconception that the Gateway API will replace the Kubernetes Ingress Controller (KIC) in the near term or make it less useful over the longer term. This view is incorrect for multiple reasons.

Event

Intelligent Security Summit

Learn the critical role of AI & ML in cybersecurity and industry specific case studies on December 8. Register for your free pass today.


Register Now

Ingress controllers are now embedded in the functional architecture of most Kubernetes deployments. They have become de facto. At some point, the Gateway API will be sufficiently mature to replace all functionality of the Ingress API and even the implementation-specific annotations and custom resources that many of the Ingress implementations use, but that day remains far off.

Today, most IT organizations are still either in the early adoption or the testing stage with Kubernetes. For many, just getting comfortable with the new architecture, networking constructs, and application and service management requirements requires considerable internal education and digestion.

Gateway API and Ingress controllers are not mutually exclusive

As we’ve done at NGINX, other Ingress maintainers will presumably implement the Gateway API in their products to take advantage of the new functionality and stay current with the Kubernetes API and project. Just as RESTful APIs are useful for many tasks, the Kubernetes API underpins many products and services, all built on the foundation of its powerful container orchestration engine.

The Gateway API is designed to be a universal component layer for managing service connectivity and behaviors within Kubernetes. It is expressive and extensible, making it useful for many roles, from DevOps to security to NetOps.

As a team that has invested considerable resources into an open source Ingress controller, NGINX could have chosen to integrate the Gateway API into our existing work. Instead, we elected to leverage the Gateway API as a standalone, more open-ended project. We chose this path so as not to project the existing constraints of our Ingress controller implementation onto ways we might hope to use the Gateway API or NGINX in the future. With fewer constraints, it is easier to fail faster or to explore new designs and concepts. Like most cloud-native technology, the Gateway API construct is designed for loose coupling and modularity ­— even more so than the Ingress controller, in fact.

We are also hopeful that some of our new work around the Gateway API is taken back into the open-source community. We have been present in the Kubernetes community for quite some time and are increasing our open-source efforts around the Gateway API.

It could be interpreted that the evolving API provides an invaluable insertion point and opportunity for a “do-over” on service networking. But that does not mean that everyone is quick to toss out years of investment in other projects. Ingress will continue to be important as Gateway API matures and develops, and the two are not mutually exclusive.

Plan for a hybrid future

Does it sound like we think the Kubernetes world should have its Gateway API cake and eat its Ingress controller too? Well, we do. Guilty as charged. Bottom line: We believe Kubernetes is a big tent with plenty of room for both new constructs and older categories. Improving on existing Ingress controllers —which were tethered to a limited annotation capability that induced complexity and reduced modularity — remains critical for organizations for the foreseeable future.

Yes, the Gateway API will help us improve Ingress controllers and unleash innovation, but it’s an API, not a product category. This new API is not a magic wand nor a silver bullet. Smart teams are planning for this hybrid future, learning about the improvements the Gateway API will bring while continuing to plan around ongoing Ingress controller improvement. The beauty of this hybrid reality is that everyone can run clusters in the way they know and desire. Every team gets what they want and need.

Brian Ehlert is director of product management at NGINX.

Source link

Continue Reading

Trending

URGENT: CYBER SECURITY UPDATE