John W. Mannion: No Disclosed Stock Trades

John W. Mannion Congressional Trading Profile | Quantellect John W. Mannion

Representative John W. Mannion, the Democrat serving New York's 22nd district since his current term began on January 3, 2025, has no disclosed securities transactions on file in Quantellect's database. That places him in large company. As measured on August 22, 2026, 276 of the 537 sitting members of Congress have zero disclosed trades on record, including 237 of the 437 sitting House members. A member with no transaction rows is not an outlier in this dataset.

Quantellect maintains a profile page for every member of Congress regardless of trading activity, because the absence of disclosed trades is itself a data point worth recording accurately. What follows explains what “no disclosed trades” means in this dataset, how periodic transaction reporting operates, and how attribution and score coverage are presented when applicable.

What “No Disclosed Trades” Means Under the STOCK Act

Members of Congress must file periodic transaction reports for purchases, sales, and exchanges involving certain securities when the transaction exceeds $1,000. Under the Stop Trading on Congressional Knowledge Act of 2012, commonly known as the STOCK Act, a report is due by the earlier of two deadlines: 30 days after the filer becomes aware of the transaction or 45 days after the transaction date. The House Committee on Ethics financial disclosure instruction guide explains the filing mechanics, threshold, deadlines, and rules covering transactions involving House members, their spouses, and dependent children.

For Mannion, the database result is unambiguous: Quantellect contains no transaction rows in the period covered by the supplied data. His total transaction count is zero, with zero purchases, zero sales, and zero other transactions. The database also contains no yearly transaction history, transaction amounts, securities, tickers, sectors, or transaction and disclosure dates for him.

When disclosed transactions do exist for a member, Quantellect records who is associated with each transaction. SELF identifies the member, SP identifies a spouse, JT identifies a joint transaction, DC identifies a dependent child, and UNKNOWN means the source record does not support a more specific attribution. An UNKNOWN entry must not be treated as evidence that the member personally executed the transaction. For Mannion, every attribution category has a count of zero, so there is no transaction record to which this framework currently applies.

Score Coverage

Quantellect does not currently report a trading-behavior score for Mannion. As of the latest published scoring date of August 21, 2026, 76 members have a score, including 73 who are current sitting members. Mannion is not among them because no score row exists for him at that date.

The supplied scoring data consequently provides no formula version, score date, score, tier, coverage state, cohort rank, or cohort size for Mannion. Quantellect does not substitute a default or estimated value on this profile. The transaction population figures and score coverage figures also have distinct measurement dates: August 22, 2026, for the sitting-member context and August 21, 2026, for the latest published scores.

Disclosure and Methodology Notes

Data on this page reflects periodic transaction reports and related disclosures processed into Quantellect's database as of the dates stated above. Mannion's zero count should be read narrowly: the database contains no transactions attributed to SELF, SP, JT, DC, or UNKNOWN. That finding does not support a broader conclusion about his personal finances or activity beyond the records represented in the dataset.

Transaction dates and disclosure dates are distinct. A transaction date identifies when the reportable event occurred, while the disclosure date identifies when its report was filed or received. Because the statutory reporting window can extend beyond the transaction date, newly filed information may appear later than the underlying event. Any future records should therefore be presented using their supplied transaction dates, disclosure dates, disclosed amount ranges, transaction types, and attribution codes.