Explore more topics
NexusTrade guides

Check and preserve a public holdings finding

Follow one Apple holding back to Berkshire’s filing, check its dates and units, then preserve a research note another reader can verify.

Jump to a section

TL;DR

Berkshire reported 227,917,808 Apple shares worth $65,950,296,923 for June 30, 2026; the filing became public August 15 and was observed in NexusTrade on October 10. Preserve those dates, units and the effective filing versions together. These are delayed reported positions, not current brokerage holdings or trade timestamps. An added or increased holding needs an earlier comparable filing, and historical research must begin at public availability.

Recorded disclosure illustration

Source-derived view of the observed Berkshire disclosure: June 30 reporting period, August 15 public availability, 29 positions and three largest reported values.
Source-derived visualization of the public NexusTrade page read October 10, 2026. This is not a screenshot or a managed-list execution receipt. Open the illustration for a full-size view.
Open the original disclosure illustration

What the public product actually shows

Show the table · 3 rows, 3 columns

Scroll sideways to compare all columns. Select a heading to sort.

AAPL — Apple$65,950,296,923227,917,808
AXP — American Express$51,282,319,275151,610,700
KO — Coca-Cola$32,508,000,000400,000,000

Read on October 10, 2026: Berkshire’s June 30, 2026 filing became publicly available on August 15. NexusTrade shows 29 reported positions worth $299,253,556,246. Apple accounts for $65,950,296,923, American Express $51,282,319,275 and Coca-Cola $32,508,000,000. Values are reported US dollars; share amounts are a different field.

These are delayed reported positions, not a live brokerage account. The 29 positions are not necessarily 29 companies or 29 managed-list members: share classes and eligibility matter. The public page records one effective filing, no unresolved ticker positions and no put/call positions for this snapshot.

Reproduce a specific finding

What did Berkshire report for June 30, 2026, and when could a researcher use it? Start with the public product page, then retain the filing versions. This is an analyst workflow; it does not promise institutional licensing, SSO or a service-level agreement.

  1. Open the Berkshire disclosure. Record the report period, public availability date, effective filing count and unresolved ticker count.
  2. Open the linked SEC filing. Confirm manager CIK 1067983 and accession 0001193125-26-352200.
  3. Keep reported value (USD) separate from shares (SH).
  4. Preserve the observation date October 10, 2026. A later amendment can change a later reconstruction.

Follow one real holding

Step 1 of 3

Inspect the recorded Apple position

Start with this recorded Apple position on Berkshire’s NexusTrade page. The filing covers June 30, 2026 and became public on August 15. These dates answer different questions.

Open Berkshire’s actual holdings
Apple shares reported
227,917,808
Apple value reported
$65,950,296,923
Holdings measured on
June 30, 2026
Available to readers on
August 15, 2026
What you should see

The recorded October 10 snapshot contains 29 reported positions. Open the linked filing to check Apple’s shares and reported dollar value.

Step 2 of 3

Keep the finding with its source

Keep Apple’s share count, reported dollar value, reporting date, public-availability date and source link together. Another reader should be able to check the same observation.

What you should see

A checkable note: Berkshire reported 227,917,808 Apple shares worth $65,950,296,923 for June 30, 2026; the filing became public August 15. Observed on NexusTrade October 10.

Step 3 of 3

Ask Aurora to check your note

Open the prepared research request. Ask for the filing link and keep any missing comparison clearly unresolved.

What you should see

An explanation you can check against the cited filing. The request does not save a watchlist or start trading.

Inspect the schema before querying

Read the detailed inspect the schema before querying

Configure Python SDK account authentication first. Read client.describe_lake_table("institutional_filings") and client.describe_lake_table("institutional_holdings"). Canonical SQL table names begin with lake. Filings have one row per submission; holdings have one row per accession and infoTableSk. Missing resolvedTicker is deliberate, not permission to guess a company.

Retain versions and bound the query

Read the detailed retain versions and bound the query

This query returns at most 20 filing-version records for one manager and a fixed availability window. It is a copyable request, not a claim that this SDK request was executed for the guide. The product receipt above was read from the public page. The query lists originals and amendments; its first row alone is not an effective holdings reconstruction.

SQL
SELECT accession, managerName, periodOfReport, availableAt,
       submissionType, isAmendment, amendmentType, sourceUrl
FROM lake.institutional_filings
WHERE ltrim(cik, '0') = ?
  AND availableAt >= TIMESTAMP '2026-01-01 00:00:00'
  AND availableAt <= TIMESTAMP '2026-10-10 23:59:59'
ORDER BY availableAt DESC, accession DESC
LIMIT 20

Submit once, poll and retain the manifest

Read the detailed submit once, poll and retain the manifest

Structured SQL invokes no text model but can consume account compute resources. Inspect account access and capacity before submitting. Row, byte and runtime limits are not a monetary quote. A failed or cancelled operation is not a zero-row result.

Python
import json
from pathlib import Path
from nexustrade import NexusTradeClient

client = NexusTradeClient.from_environment()
operation = client.create_lake_query(
    {"query": Path("filing-versions.sql").read_text(), "params": ["1067983"],
     "limits": {"timeoutSeconds": 30, "maxRows": 20,
                "maxResultBytes": 1048576}},
    idempotency_key="berkshire-filing-versions-20261010-v1",
)
finished = client.wait_for_lake_query(operation["id"])
if finished["status"] != "completed":
    raise RuntimeError(finished)
manifest = client.get_lake_query_manifest(operation["id"])["result"]
Path("filing-versions-manifest.json").write_text(json.dumps(manifest, indent=2))
for part in manifest["parts"]:
    Path(f"filing-versions-{part['part']}.parquet").write_bytes(
        client.download_lake_query_part(operation["id"], part["part"],
                                        max_bytes=1048576)
    )
print("Rows:", manifest["rowCount"], "Catalog:", manifest["catalogVersion"])

Reconcile before using the result

Read the detailed reconcile before using the result

Reported holdings are delayed long-only snapshots, not entry timestamps or current brokerage positions. A historical strategy must use availableAt, not periodOfReport, as the earliest decision date.

  1. Retain the SQL, bind values, SDK version, catalogVersion, rowCount and each part’s sha256 beside the research note.
  2. Compare originals and amendments at the same availability cutoff. A RESTATEMENT replaces its prior version; NEW HOLDINGS adds positions.
  3. Join holdings to filings on accession. Sum positive normalized USD values after selecting effective versions; never join a manager name to an issuer ticker.
  4. Reconcile the period, total and unresolved securities against the public page. Explain mismatches instead of silently dropping rows.
  5. If the response is lost, reuse the original idempotency key with identical inputs. Preserve a failed operation before deliberately submitting a corrected request.

Continue exploring

Discussion

Sign in or create a free account to join the discussion.

No comments yet.

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.