4 measurements spanning 15 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 361–363 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 18:57
363
+2
16 Aug 2026, 05:46
361
-1
8 Aug 2026, 06:33
362
no change
7 Aug 2026, 21:53
362
first reading
Engagement
18 posts held, back to 13 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
39 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 51.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
20
51.3%
❤
18
46.2%
😁
1
2.56%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 39reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 November 2025 to 19 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
3
of 18 we hold a reading for · 17%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @loadvid. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 18 most recent posts we hold for this entry, published 13 November 2025 to 19 May 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Dear users,
We will be performing scheduled maintenance for approximately 30 minutes to improve system stability and ensure better video loading performance.
During this time, some services may be temporarily unavailable or experience interruptions.
We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to provide a better experience.
Thank you for your support.
Dear users,
We are currently experiencing hardware and network-related issues affecting the server infrastructure, specifically involving disk stability and upstream connectivity.
Please rest assured that all data has been fully backed up and secured. No data loss is expected.
To ensure long-term stability and better performance, we will be migrating to a new server environment tomorrow. The migration process is e…
Any attempt to upload or distribute child sexual abuse material (CSAM/CP) will result in an immediate and permanent ban. No warnings, no appeals.
This platform has zero tolerance for such content. All violations may be reported to the appropriate authorities.
Do not test this policy.
System Maintenance Notice
Our system is currently undergoing maintenance to improve performance and stability.
Estimated maintenance time: 15-20 minutes.
During this period, some services may be temporarily unavailable.
We appreciate your patience and understanding while we complete the update.
Thank you for your support! 🚀
Support Announcement – We Are Moving to Session Chat
To provide faster response times and maximum privacy, we are moving our customer support to Session Chat.
Session is a secure, end-to-end encrypted messaging app that does not require a phone number and stores no centralized user data, making it one of the most private ways to communicate online.
You can contact our support team using the following Session ID:
05…
Optimizing CDN for Users with High Traffic in Asia
We would like to inform users who receive a significant amount of traffic from Asia, particularly Southeast Asia, that we can optimize your content delivery for better performance.
If a large portion of your viewers are located in these regions, please contact our support team at [email protected]. Our team will review your traffic distribution and, if applicable…
💋 The upload issue has now been resolved. We sincerely apologize for any inconvenience caused and appreciate your patience during the maintenance period
Some members have been asking why their videos are only 2–3 minutes long but still take quite a while to encode.
The reason is that we recently updated our upload workflow:
User upload → HLS encoding → upload to S3 → publish to the player.
It’s a first-come, first-served queue — those who upload earlier get processed first, and those who upload later will need to wait.
However, this process ensures that your videos…
Showing the 12 most recent of 18 posts we hold for @loadvid. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“LoadVID Announcement 🪭” (@loadvid), 363 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/loadvid.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.