The activity figures on FreeUSSMS number pages describe retained message records for numbers currently listed in our public directory, at a recorded snapshot time. They help you compare recent activity without opening message text. They are not a test score, a permanent archive or a promise that your next text will arrive.
What is counted
The source is the service’s stored message records and number-directory history. The snapshot is limited to number-and-ID pairs in the current public directory. Numbers absent from that directory, including private numbers that are not publicly listed, are excluded. Removed records no longer contribute.
For a publicly listed number, retained records can contribute to a count even when privacy controls hide their text. An aggregate count therefore need not match the number of message cards a visitor can read. The snapshot process reads timestamps, not message senders, message bodies or verification codes; the public summaries expose only counts and timestamps. Reading the inbox remains a separate, free browser flow with browser checks and fair-use protections.
How to read each figure
| Figure | Meaning |
|---|---|
| Retained messages | The number of stored message records for this currently public-listed number, including records whose text is hidden by privacy controls. It is not the number of all messages ever received, visitors, account registrations or successful requests. |
| Earliest retained message | The oldest received timestamp among the messages included in the snapshot. It can move forward when older messages are removed. It is not the number’s activation date. |
| Latest retained message | The newest received timestamp among the included messages. It describes a recorded arrival, not a promise that the line is receiving right now. |
| First listed in our directory | The earliest record for the number in our synchronized directory history. It is not a carrier activation date, a continuous-uptime measure or a guarantee that the number was available every day since. |
| Last 24 hours | Included messages with received timestamps inside the rolling 24-hour window ending at the snapshot time. |
| Last 7 days | Included messages inside the rolling 168-hour window ending at the snapshot time. |
| Daily activity / active days | Seven UTC calendar dates: the snapshot’s current date and the six preceding dates. An active day has at least one included message. The current day is partial. |
Rolling windows and UTC calendar days are different
Daily rows use UTC midnight boundaries, not your browser’s local midnight. Rolling windows end at the snapshot’s exact time. For example, a snapshot at 12:00 UTC covers the preceding 168 hours for “last 7 days,” while its seven daily rows start at 00:00 UTC six calendar dates earlier. The rolling window also includes part of the date before those rows.
As a result, the sum of the seven daily rows can differ from the rolling seven-day count. An active-day count describes those seven calendar dates, not seven complete 24-hour periods. The timestamps and labels on the number page identify the snapshot to use when comparing figures.
Freshness and missing data
The public activity snapshot is normally rebuilt about every five minutes. The snapshot time records when these figures were calculated; the latest-message time records a message arrival. They answer different questions. A new text may appear in the protected inbox before it appears in these aggregate figures.
If a snapshot is more than fifteen minutes old, the page withholds its detailed aggregate figures and shows a delayed-data explanation rather than presenting them as current. An absent or delayed summary is not a claim of zero messages. Refreshing a page does not force an immediate snapshot rebuild.
Number availability and message retention can change. Counts may decrease after records are removed or a number leaves the public directory; the website does not preserve a permanent history for each visitor. A saved-number shortcut does not reserve the line or its message history.
What activity does not prove
- No delivery percentage: the website does not observe every request sent to an outside provider. A received-message count has no complete request denominator, so it is not a delivery success rate.
- No account outcome: receiving a text does not establish that registration, login or account recovery finished successfully.
- No future acceptance: each sending service applies its own number requirements and risk checks. Recent activity and a physical SIM do not guarantee acceptance of a shared number.
- No identity or location inference: an area code is numbering context, not proof of a visitor’s identity, present location or eligibility.
Public data and private rentals
The free public inbox is shared, even after a browser check. A private rental is a separate, time-limited product with its own current price and conditions; it is not ownership of a number. Use a number you control for private messages or long-term account recovery. Read the public inbox privacy guidance and the public-versus-private comparison.
Questions and corrections
For an apparent mismatch, note the number-page URL, the displayed snapshot time and which figures you compared. The FreeUSSMS team and correction channel explain where to send that information. Do not share verification codes or private account details. For a missing requested text rather than a data-definition question, use the SMS troubleshooting guide.
Page updated . Number availability and activity have their own snapshot times.