FY2001 · period end Dec '01 · from the 10-K filed Mar 4, 2002
| Metric | FY01Dec '01 |
|---|---|
| Revenue | $9.81B |
| Gross Profit | — |
| Operating Income | $1.89B |
| Net Income | — |
| EPS (Diluted) | — |
| Metric | FY01Dec '01 |
|---|---|
| Total Assets | $25.40B |
| Total Liabilities | — |
| Stockholders' Equity | $4.14B |
| Cash & Equivalents | $0.17B |
| Total Debt | — |
| Metric | FY01Dec '01 |
|---|---|
| Operating Cash Flow | $1.34B |
| Capital Expenditures | — |
| Free Cash Flow | — |
| Metric | FY01Dec '01 |
|---|---|
| Gross Margin | — |
| Operating Margin | 19.3% |
| Net Margin | — |
| Return on Equity | — |
| Return on Assets | — |
| Debt / Equity | — |
Showing the most recent 1 annual periods. Get 15 years of history on the Pro plan, or unlimited history back to 1993 plus the smart-money dataset and webhooks on Institutional.
| Form | Accession ID | Report Date | Filing Date | Accepted At | Source |
|---|---|---|---|---|---|
| 8-K | 0001193125-26-255562 | Jun 1, 2026 | Jun 3, 2026 | Jun 3, 2026 20:30 UTC | EDGAR |
| 8-K | 0001193125-26-173855 | Apr 21, 2026 | Apr 23, 2026 | Apr 23, 2026 20:35 UTC | EDGAR |
| 8-K | 0001193125-26-018045 | Jan 20, 2026 | Jan 21, 2026 | Jan 21, 2026 21:30 UTC | EDGAR |
| 8-K | 0001193125-25-097067 | Apr 22, 2025 | Apr 25, 2025 | Apr 25, 2025 20:51 UTC | EDGAR |
| 8-K | 0001193125-25-050925 | Mar 6, 2025 | Mar 10, 2025 | Mar 10, 2025 20:30 UTC | EDGAR |
| 8-K | 0000950170-24-128681 | Nov 18, 2024 | Nov 19, 2024 | Nov 19, 2024 21:33 UTC | EDGAR |
| 8-K | 0001193125-24-220162 | Sep 11, 2024 | Sep 17, 2024 | Sep 17, 2024 12:30 UTC | EDGAR |
| 8-K | 0001193125-24-102953 | Apr 16, 2024 | Apr 19, 2024 | Apr 19, 2024 20:31 UTC | EDGAR |
Direct links to SEC EDGAR. PEG has additional filings available on the SEC site.
6 numbers PUBLIC SERVICE ENTERPRISE GROUP INC later changed — same XBRL tag, both filings linked.
Operating Income (Loss)·Q3 2009
Notable restatementwas$924M
Revised down in a 10-K.
Revenues·FY 2008
Notable restatementwas$13.3B
Revised down in a 10-K. Any P/S built on the original was 5.7% too low.
Operating Income (Loss)·FY 2008
Notable restatementwas$2.6B
Revised down in a 10-K.
Revenues·Q3 2009
Notable restatementwas$3B
Revised down in a 10-K. Any P/S built on the original was 5.0% too low.
Revenues·Q3 2010
Notable restatementwas$3.3B
Revised down in a 10-K. Any P/S built on the original was 4.5% too low.
Operating Income (Loss)·Q3 2010
Notable restatementwas$1B
Revised down in a 10-K.
PEG is not the only one.
See every restatement we've found across the market — or get an alert the next time PEG revises a number.
Restatements are detected by comparing every vintage of a fact across all of PUBLIC SERVICE ENTERPRISE GROUP INC's filings back to 1993. A revision is not by itself a sign of wrongdoing — companies re-file for many legitimate reasons. This list is not exhaustive: it shows PEG's most significant revisions, and a figure absent from it has not been certified as unrevised.
Who is buying and selling PUBLIC SERVICE ENTERPRISE GROUP INC — insider transactions from Forms 3/4/5/144 and institutional ownership from 13F, 13D, and 13G filings, point-in-time stamped like every other fact in the library. Traders read it as a positioning signal; risk desks read it as concentration.
No published research on PEG yet.
Reports appear here as analysts publish research on this company — built with Valuein's agentic workflows, every figure pinned to its SEC filing. Be the first: run equity_research_brief on PEG and publish the result to your public profile.
Ask about PUBLIC SERVICE ENTERPRISE GROUP INC
Continue in Workspace — cited answers on PEG, a thesis you can score, or a signal on the next filing.
Open in WorkspaceGet 15 years of data
Quarterly and annual financials back to 2011 on Pro (1993 on Institutional). Point-in-time accurate with zero survivorship bias.
View plansQuery via Python SDK
Pull data into DuckDB with 3 lines of Python. Works in Jupyter notebooks, scripts, and CI pipelines.
SDK docsConnect via MCP Server
Wire Claude, Cursor, or Codex directly to live SEC data with a single Bearer token. No scraping, no glue code.
MCP docs