Feeds

LinkedIn whips out begging cap, asks for $500m

Please, sir, can I have some more?

Boost IT visibility and business value

LinkedIn is looking for a few million dollars more from the market so it can increase its capital and its public float.

The social business network wants to raise the funds with a secondary offering of around $100m worth of its own shares, with another $400m or so coming in from stocks sold by existing holders.

"The proceeds of the primary portion of the offering will be used to provide additional working capital for LinkedIn, including further expansion of its product development and field sales organisations, for capital expenditures and potential strategic acquisitions or investments," LinkedIn said in a canned statement.

LinkedIn, which went public in May, has had a fairly tumultuous time on the open market so far. Its shares, initially priced at $45, soared on debut to $94.25, fell back to under $64 in June and soared again to $109 in July before settling to a more-than-respectable value of between $85 and $92 in the last three months.

The web company has just released its financial results for the third quarter of this year, featuring a net loss of $1.6m, despite revenues that had increased 126 per cent to $139.5m.

LinkedIn makes its money from its premium user subscriptions and from helping companies on the network hire staff and market themselves.

Its hiring solutions made the lion's share of its revenues in the three months ending in September, bagging $70.9m, while marketing solutions earned $40m and subscriptions made $28.4m.

LinkedIn said it was predicting revenue in the fourth quarter of between $154m and $158m and full-year revenue to be $508m to $512m, but it didn't make any predictions on its net income or loss for these periods.

The networking firm preferred, as companies often do, to concentrate its expectations on adjusted EBITDA, an accounting term that basically means earnings before taxes, interest payments on loans or the reduction in the value of its assets. By that metric, the firm actually made $24.7m in the third quarter instead of losing $1.6m.

LinkedIn is forecasting adjusted EBITDA of $19m to $21m next quarter and $83m to $85m for the full year. ®

Build a business case: developing custom apps

More from The Register

next story
6 Obvious Reasons Why Facebook Will Ban This Article (Thank God)
Clampdown on clickbait ... and El Reg is OK with this
Mozilla's 'Tiles' ads debut in new Firefox nightlies
You can try turning them off and on again
No, thank you. I will not code for the Caliphate
Some assignments, even the Bongster decline must
Kaspersky backpedals on 'done nothing wrong, nothing to fear' blather
Founder (and internet passport fan) now says privacy is precious
Banking apps: Handy, can grab all your money... and RIDDLED with coding flaws
Yep, that one place you'd hoped you wouldn't find 'em
TROLL SLAYER Google grabs $1.3 MEEELLION in patent counter-suit
Chocolate Factory hits back at firm for suing customers
Primetime precrime? Minority Report TV series 'being developed'
I have to know. I have to find out what happened to my life
Ex-IBM CEO John Akers dies at 79
An era disrupted by the advent of the PC
prev story

Whitepapers

Gartner critical capabilities for enterprise endpoint backup
Learn why inSync received the highest overall rating from Druva and is the top choice for the mobile workforce.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Consolidation: The Foundation for IT Business Transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.