Create Account
Log In
Dark
chart
exchange
Premium
Terminal
Screener
Stocks
Crypto
Forex
Trends
Depth
Close
Check out our API

PIT
VanEck Commodity Strategy ETF
stock BATS ETF

At Close
Oct 1, 2026 2:05:00 PM EDT
82.82USD+0.963%(+0.79)79,566
0.00Bid   0.00Ask   0.00Spread
Pre-market
Oct 1, 2026 8:08:30 AM EDT
92.57USD+12.849%(+10.54)200
After-hours
Oct 1, 2026 4:42:30 PM EDT
82.96USD+0.169%(+0.14)1,309
OverviewOption ChainMax PainOptionsPrice & VolumeDividendsHistoricalExchange VolumeDark Pool LevelsDark Pool PrintsExchangesShort VolumeShort Interest - DailyShort InterestBorrow Fee (CTB)Failure to Deliver (FTD)ShortsTrends
PIT Reddit Mentions
Subreddits
Limit Labels     

We have sentiment values and mention counts going back to 2017. The complete data set is available via the API.
Take me to the API
PIT Specific Mentions
As of Oct 2, 2026 4:47:28 AM EDT (<1 min. ago)
Includes all comments and posts. Mentions per user per ticker capped at one per hour.
14 hr ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
Your version/correction point also raises a deeper question. Suppose a vendor originally stored a constituent state as v1, later discovered an error and created v2. For a historical query whose as-of date precedes the correction, should a genuine PIT system still reproduce v1, while a later query can see v2? If the vendor instead silently returns v2 for every historical date, would you consider that historical revision rather than PIT knowledge? Have you personally encountered a system that preserves this kind of supersession lineage?
sentiment -0.30
14 hr ago • u/drhobbi • r/quant • what_to_do_with_alpha_signal_but_no_capital_to • C
Thank you so much! Once I have the sim results, would you mind if I post them here to get your feedback on them? You know your stuff!
I've already incorporated data, feature, code versioning with a comprehensive ML and data Ops framework but thank you for the suggestion!
I already have comprehensive known at timestamps with comprehensive PIT guardrails and also handle survivorship bias with ticker reuse and delisted ticker handling but thanks for raising this too!
I went over engineered on the platform to build an automated metadata driven framework and a harness - attached
https://preview.redd.it/xfblguxfhwsh1.png?width=3600&format=png&auto=webp&s=b7385e7c17ab96f70a0a81d685dcc3ff23739854
sentiment 0.91
15 hr ago • u/Shoddy_Peanut7320 • r/quant • looking_for_historical_sp_500_constituent_data • C
I'm speaking from general PIT and data-engineering knowledge, not experience with a specific vendor, and I can't name a dataset I'd vouch for. I'd rather say that than hand you a lead I haven't verified.
Your hierarchy is about right, with one tweak: the announcement sets the knowledge time, and the ETF holdings and auction evidence only corroborate the effective date. If an ETF file shows a change a day off from the official date, I'd keep the S&P date as authoritative, record the ETF gap as lag, and never let a holdings file published afterward move the knowledge time. ETF files only count as evidence if you captured them yourself at publication time.
Five tests I'd run on a Mar to Sep 2026 dataset:
1. Flag any record whose effective\_from precedes its first public announcement. There should be none, apart from same-day cases.
2. Look at the lag between announcement and effective date. A genuine capture shows a spread of lags, while a backfill shows zero or a constant.
3. Compare the vendor's history pulled now to snapshots you captured earlier, and check that every past change shows up as a versioned correction.
4. Check auction volume on the day before each effective date, and that pending-merger names stay members until the close date.
5. Check identifier continuity across ticker changes and mergers.
sentiment 0.75
1 day ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
The bitemporal point is exactly the distinction we're trying to enforce: valid/effective time vs knowledge/as-of time.
Could you clarify what you would consider the minimum vendor schema for proving true PIT?
For example, would you require fields equivalent to:
- effective_from / effective_to
- first_available_at
- vendor_as_of / knowledge_time
- version_id
- correction/supersession flag
- immutable raw response or snapshot hash
And one key question: how would you distinguish a genuinely historical record from a modern backfill that was simply assigned an old effective date?
If you have seen a vendor that actually preserves this distinction in production, naming the vendor (even privately/publicly documented features only) would be extremely valuable.
sentiment 0.86
14 hr ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
Your version/correction point also raises a deeper question. Suppose a vendor originally stored a constituent state as v1, later discovered an error and created v2. For a historical query whose as-of date precedes the correction, should a genuine PIT system still reproduce v1, while a later query can see v2? If the vendor instead silently returns v2 for every historical date, would you consider that historical revision rather than PIT knowledge? Have you personally encountered a system that preserves this kind of supersession lineage?
sentiment -0.30
14 hr ago • u/drhobbi • r/quant • what_to_do_with_alpha_signal_but_no_capital_to • C
Thank you so much! Once I have the sim results, would you mind if I post them here to get your feedback on them? You know your stuff!
I've already incorporated data, feature, code versioning with a comprehensive ML and data Ops framework but thank you for the suggestion!
I already have comprehensive known at timestamps with comprehensive PIT guardrails and also handle survivorship bias with ticker reuse and delisted ticker handling but thanks for raising this too!
I went over engineered on the platform to build an automated metadata driven framework and a harness - attached
https://preview.redd.it/xfblguxfhwsh1.png?width=3600&format=png&auto=webp&s=b7385e7c17ab96f70a0a81d685dcc3ff23739854
sentiment 0.91
15 hr ago • u/Shoddy_Peanut7320 • r/quant • looking_for_historical_sp_500_constituent_data • C
I'm speaking from general PIT and data-engineering knowledge, not experience with a specific vendor, and I can't name a dataset I'd vouch for. I'd rather say that than hand you a lead I haven't verified.
Your hierarchy is about right, with one tweak: the announcement sets the knowledge time, and the ETF holdings and auction evidence only corroborate the effective date. If an ETF file shows a change a day off from the official date, I'd keep the S&P date as authoritative, record the ETF gap as lag, and never let a holdings file published afterward move the knowledge time. ETF files only count as evidence if you captured them yourself at publication time.
Five tests I'd run on a Mar to Sep 2026 dataset:
1. Flag any record whose effective\_from precedes its first public announcement. There should be none, apart from same-day cases.
2. Look at the lag between announcement and effective date. A genuine capture shows a spread of lags, while a backfill shows zero or a constant.
3. Compare the vendor's history pulled now to snapshots you captured earlier, and check that every past change shows up as a versioned correction.
4. Check auction volume on the day before each effective date, and that pending-merger names stay members until the close date.
5. Check identifier continuity across ticker changes and mergers.
sentiment 0.75
1 day ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
The bitemporal point is exactly the distinction we're trying to enforce: valid/effective time vs knowledge/as-of time.
Could you clarify what you would consider the minimum vendor schema for proving true PIT?
For example, would you require fields equivalent to:
- effective_from / effective_to
- first_available_at
- vendor_as_of / knowledge_time
- version_id
- correction/supersession flag
- immutable raw response or snapshot hash
And one key question: how would you distinguish a genuinely historical record from a modern backfill that was simply assigned an old effective date?
If you have seen a vendor that actually preserves this distinction in production, naming the vendor (even privately/publicly documented features only) would be extremely valuable.
sentiment 0.86
2 days ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
### 6. ETF holdings are especially interesting
You called them “semi-independent,” which sounds right.
But there is a subtle problem:
If an ETF tracks the S&P 500, its holdings are not an independent definition of the index.
However, if we observe:
T-1 ETF holding = A
T ETF holding = B
S&P says A→B effective before open T
then the ETF provides evidence that the transition was actually implemented.
So I would classify it as something like:
INDEX_MEMBERSHIP authority: NO
IMPLEMENTATION_CORROBORATION: YES
Would you agree?
And would you consider multiple ETF sponsors useful here?
For example:
- State Street SPY
- BlackRock IVV
- Vanguard VOO
If all three independently show the same transition, does that meaningfully strengthen the evidence, or do you still regard them as largely downstream of the same S&P source?
---
### 7. Closing-auction volume — I want to challenge this one
You mentioned closing-auction volume spikes as evidence that index funds actually traded.
Interesting idea, but I’m not convinced it is sufficient.
A volume spike on T-1/T could be caused by many things unrelated to the S&P 500 transition.
Would you require something like:
candidate transition
+
abnormal closing volume
+
price/auction behavior
+
ETF holdings transition
+
official effective date
before treating it as implementation corroboration?
Or do you think auction-volume evidence can independently establish anything stronger?
---
### 8. Corporate-action timestamping
Your suggestion to tag every deletion with the triggering corporate event is exactly the direction I’m moving toward.
But I want to distinguish at least:
EVENT_TIME
when the corporate action legally/economically occurred
ANNOUNCEMENT_TIME
when it was announced
INDEX_EFFECTIVE_TIME
when S&P actually changed the index
MARKET_EFFECTIVE_TIME
when the new constituent could actually trade as an index constituent
OBSERVATION_TIME
when our data source first recorded it
These can all differ.
Do you think this is the correct event model?
And for something like a merger/delisting/spin-off, what would you use as the primary timestamp authority for each one?
---
### 9. Cymetica / EventTrader
You mentioned Cymetica’s EventTrader.
Can you be more specific about what you have actually seen from it?
Does it provide:
- event timestamp
- event type
- security identifier
- announcement timestamp
- effective timestamp
- source document
- original vs corrected event
- or merely a normalized corporate-action calendar?
And most importantly:
Is its historical data point-in-time frozen, or is it a continuously maintained/revised historical database?
I don’t need marketing claims here.
I’m interested in the exact data semantics.
---
### 10. The September question
September is not actually the only issue in my data.
That is one of the interesting findings.
One source has a coverage gap beginning in August, while another full-window daily source covers the entire research window but has a small number of disagreements.
The full-window source currently has:
127/127 historical dates covered
but:
120 exact set matches
and:
7 raw ticker-set mismatches.
The seven are not all the same type of problem.
Two are clearly ticker-identity transitions:
- BK → BNY
- SATS → ECHO
Several others appear to be source-update/effective-date lag around events such as:
- FDXF / EPAM
- HONA
- FERG / EA
The important point is that my validator deliberately does NOT silently normalize these into MATCH.
A raw ticker-set difference remains:
MISMATCH
even if forensic analysis later explains the difference.
That is intentional because I don’t want the validator itself to “fix” a source until we’ve independently established why the difference exists.
So the current state is approximately:
formal PIT membership gate: NOT ADMITTED
but
forensic evidence: no currently unexplained contradiction identified in those seven cases.
Would you consider that the correct interpretation?
---
### 11. One more thing I’d really like your opinion on
If you were designing this from scratch, would you create separate evidence classes like:
A. MEMBERSHIP AUTHORITY
- S&P DJI
B. CORPORATE-ACTION AUTHORITY
- SEC/company primary filings
C. IMPLEMENTATION CORROBORATION
- SPY/IVV/VOO holdings
- index-fund trading/auction evidence
D. HISTORICAL RECONSTRUCTION
- GitHub / Wikipedia / public datasets
E. AGGREGATE CONSISTENCY
- index level
- divisor
- market-cap reconstruction
F. SECURITY IDENTITY
- CUSIP / ISIN / FIGI / issuer identifiers
and then explicitly prohibit evidence from one class from masquerading as evidence for another?
That is increasingly looking like the cleanest architecture to me.
I’m less interested in finding “another dataset that agrees with ours” now.
I’m interested in constructing an evidence system where each independent evidence class proves a different property, and where a failure in one layer cannot be hidden by agreement in another.
If you think that architecture is sound, I’d also be interested in hearing what evidence class you think I’m still missing.
And one final question:
If you were forced to choose only THREE additional investigations to perform next, which three would you choose, and exactly what would you try to prove or falsify with each one?
I’m looking specifically for investigations that can materially change the admission/rejection decision, not just produce more documentation.
sentiment 0.99
2 days ago • u/Wild-Raspberry-1770 • r/quant • looking_for_historical_sp_500_constituent_data • C
Woaah,you are my best friend 😅 this is much more useful, thanks. I agree with most of the distinctions you’re making, but I want to push the question one level deeper because this is exactly where I’m trying to make the research architecture robust rather than merely “plausible.”
I’m building a point-in-time historical S&P 500 constituent dataset for a 15-minute research/replay system. The critical requirement is not simply “what is the S&P 500 today?” but:
What was the constituent set at each historical timestamp, using only information that was actually valid/available at that time?
So I’m deliberately separating:
- historical truth
- historical knowledge
- valid time
- known/as-of time
- announcement time
- effective time
- observation time
- later-restated data
A few follow-ups based on your answer:
### 1. Divisor — I agree it should not be a membership validator
Your explanation actually strengthens my suspicion that the divisor belongs in a completely separate consistency layer.
S&P DJI’s methodology makes the divisor part of the mechanism used to preserve index continuity when additions/deletions, share-count changes, IWF changes and other non-price events occur.
So I would not use:
“divisor agrees → constituent membership is correct”
That would clearly be circular.
Instead, I’m thinking of a much weaker test:
Given a candidate constituent transition, observed prices, estimated shares/IWFs and the index level, does the implied index-market-value transition fall within a plausible range?
In other words:
divisor = aggregate sanity check, not membership evidence.
Do you agree with that architecture?
And more importantly:
Have you ever seen a genuinely public historical source containing actual S&P 500 divisor values with dates/effective timestamps, rather than a derived/implied series?
If yes, I’d be very interested in the exact source.
If no, would you consider an implied-divisor reconstruction from independently sourced prices + shares + IWFs useful at all, or is the circularity too severe for research-grade validation?
---
### 2. There is an important distinction I want to test in your answer
You said:
“I’d treat it as a coarse sanity check, such as whether the implied change on an event date is roughly consistent with the swap.”
What exactly would you regard as a useful failure?
For example, suppose:
T-1: constituent A
T: constituent B
and the official index level remains continuous.
Would you expect a reconstruction to distinguish between:
1. wrong constituent
2. correct constituent but wrong effective timestamp
3. correct constituent and timestamp but wrong shares
4. correct shares but wrong IWF
5. corporate-action adjustment
6. stale price
7. stale ETF holding
8. insufficient precision in the public inputs
If so, that suggests divisor analysis could become a diagnostic classifier, rather than a validator.
That would be much more interesting to me.
---
### 3. Bloomberg / LSEG — can we make this concrete?
This is probably the biggest thing I’d like to extract from you.
You correctly highlighted the danger of restated history.
For a PIT research system, “historical data” is not enough.
I need to know whether the vendor can answer:
“What did the vendor believe the constituent set was at timestamp X, using the information available at timestamp X?”
rather than:
“What does the vendor’s current database say the constituent set was on timestamp X?”
Those are fundamentally different datasets.
If you had access to a Bloomberg or LSEG specialist, what exact questions/fields/API objects would you ask them for?
For example, I would want to establish whether they expose some combination of:
- index constituent membership
- effective-from timestamp
- effective-to timestamp
- announcement timestamp
- source/as-of timestamp
- revision timestamp
- original vs corrected record
- security identifier
- historical ticker
- CUSIP/ISIN
- index weight
- shares used by the index
- IWF / float factor
- corporate-action event ID
- deletion reason
- addition reason
But I suspect the really important question is whether there is an explicit distinction between:
VALID_TIME — when the constituent relationship was true
and
KNOWN_TIME / AS_OF_TIME — when the vendor actually knew/published it.
Do Bloomberg or LSEG actually expose enough information to reconstruct that distinction?
And if you don’t know the answer, what would you ask the vendor so that they cannot answer with a vague “yes, we have historical data”?
---
### 4. The “restated history” problem deserves a concrete test
Suppose Bloomberg/LSEG gives me:
AAPL ∈ S&P 500 on 2026-06-30
That is useless by itself.
What I really need to know is whether that record is:
A) a frozen historical observation captured on 2026-06-30
or
B) today’s database reconstructing what supposedly happened on 2026-06-30.
Do you know of a standard vendor concept or dataset architecture that explicitly preserves this distinction?
And if not, how would you empirically test a vendor for look-ahead/restatement?
For example, would you request:
“Give me the constituent history as it would have been retrieved on July 1, 2026”
and compare that with:
“Give me the same history today”
and then investigate every difference?
That seems like a potentially powerful vendor validation test.
---
### 5. Independent corroboration — I think this is where your answer gets particularly interesting
I agree that GitHub datasets should generally be treated as one lineage rather than five “independent sources.”
In fact, that’s exactly the problem I’ve been finding.
Some public constituent histories appear independent at first glance, but their provenance eventually converges on Wikipedia, the same upstream dataset, or another derivative.
So I’m increasingly thinking in terms of provenance graphs, not source counts.
For example:
S&P DJI press release
→ primary announcement
company 8-K / corporate-action filing
→ primary corporate event
ETF sponsor holdings
→ independent observation pipeline, but not necessarily independent membership authority
GitHub dataset
→ potentially derivative observation
Wikipedia
→ secondary compilation
That leads to a question:
What would you consider the strongest truly independent corroboration of a historical constituent transition?
Not “another website saying the same thing.”
I mean evidence generated through a genuinely different mechanism.
You mentioned:
- company 8-Ks
- corporate-action filings
- ETF holdings
- closing-auction volume
Could you rank these conceptually by what question they can actually prove, without treating one as universally superior?
For example:
Evidence | Membership? | Effective timestamp? | Announcement timestamp? | Actual implementation?
S&P DJI announcement | ? | ? | ? | ?
Company 8-K | ? | ? | ?
sentiment 1.00


Share
About
Pricing
Policies
Markets
API
Info
tz UTC-4
Connect with us
ChartExchange Email
ChartExchange on Discord
ChartExchange on X
ChartExchange on Reddit
ChartExchange on GitHub
ChartExchange on YouTube
© 2020 - 2026 ChartExchange LLC