From: matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] "Hard Pressed" Lucent News
Date: Thu, 24 Jul 2003 10:49:07 +0100 [thread overview]
Message-ID: <3F1FAB93.9040100@proweb.co.uk> (raw)
http://theregister.co.uk/content/5/31914.html
At last some good news for Lucent, the hard-pressed networking equipment
vendor. Yesterday it won a $1bn contract to supply 3G infrastructure kit
to Sprint, the US mobile network.
http://www.lucent.com/press/0703/030723.coa.html
* - Posts revenues of $1.96 billion for the quarter, a decline of 18
percent from the second fiscal quarter
- Records loss per share of 7 cents, continuing sequential improvement
on the bottom line
- Reports $4.9 billion balance in cash and short-term investments
*
The company's net loss for the quarter was $254 million or 7 cents per
share^1 . These results compare with a loss of $351 million or 14 cents
per share in the second quarter of fiscal 2003 and a net loss of $8.03
billion or $2.35 per share in the year-ago quarter.
*
*
reply other threads:[~2003-07-24 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F1FAB93.9040100@proweb.co.uk \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).