Channel
@KingTelegramUser
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001837198966 |
|---|---|
| Type | Channel |
| Username | @KingTelegramUser |
| Created | 28 May 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 5 November 2026 |
| On Telegram | t.me/KingTelegramUser |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 22 October 2026 and assigned it the closest of 31 fixed categories, at 82% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @KingTelegramUser/3 · this entry28 May 2023, 21:39 UTC | @GetStartedTelegram/328 May 2023, 21:52 UTC | 1.00 | 14 minutes |
| @KingTelegramUser/4 · this entry28 May 2023, 21:40 UTC | @GetStartedTelegram/428 May 2023, 21:53 UTC | 1.00 | 13 minutes |
| @KingTelegramUser/5 · this entry28 May 2023, 21:44 UTC | @GetStartedTelegram/528 May 2023, 21:54 UTC | 1.00 | 10 minutes |
| @KingTelegramUser/6 · this entry30 May 2023, 15:57 UTC | @GetStartedTelegram/1530 May 2023, 15:58 UTC | 1.00 | under a minute |
| @GetStartedTelegram/179 Jul 2023, 16:54 UTC | @KingTelegramUser/7 · this entry9 Jul 2023, 16:54 UTC | 1.00 | under a minute |
| @KingTelegramUser/9 · this entry25 Feb 2024, 08:32 UTC | @GetStartedTelegram/1925 Feb 2024, 08:34 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @GetStartedTelegram | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3 minutes | this entry (5–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 28 May 2023 to 7 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @KingTelegramUser — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Oct 2026, 20:42 | 7 | +1 |
| 20 Aug 2026, 18:13 | 6 | -1 |
| 14 Aug 2026, 03:08 | 7 | +1 |
| 12 Aug 2026, 21:31 | 6 | no change |
| 6 Aug 2026, 22:39 | 6 | first reading |
11 posts held, back to 28 May 2023 — 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 page of 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 11 posts for this entry, the most recent from 7 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
6 minutes that will change your life on Telegram FOREVER! We are showing JUST SOME!!! of the features available, which make TELEGRAM THE BEST SOCIAL WORLDWIDE! (even if people still don't understand that 🤦♂️ ...) https://t.me/NoComparisonTelegram YES, TELEGRAM IS THE BEST SOCIAL FOR SCIENCE TOO! https://t.me/GenRevolutionOfficial/212 More infos https://t.me/JoinShareableChatFolders/16 Music by https://t.me/Pikayz
Telegram @JoinShareableChatFolders for Dummies: a) we noticed now, that no premium user cannot see more than 100 channels ... in this case you can use for example our max 100 channel list https://t.me/addlist/eaqHVCVl4lZlYTIx https://t.me/addlist/q0dAcDb0RSc5NmQx until Telegram fix such issue in some ways ... b) you DON'T NEED to join all channels if you are not interested. You can join all and remove them later or…
Sticker, posted without a caption
True TikTokFreaks should already know that both apps are necessary for a proper usage, but Telegram Stable / Beta remain without discussion the winner!
One of the worse thing a Telegram user can do is thinking "i don't need two Mac Apps!". Never and again NEVER! use just one Mac App, except if you want to be like average users missing 50% of the features without even be able to find Telegram channels properly! Both apps are totally different and cannot be considered as alternative.
If you are using Telegram Desktop based Mac Apps (Bettergram, Desktop, Kotatogram, iMe, Telegreat, Telegram Lite, Desktop Beta), then you need to change at least one option: 1: Setting / Advanced / Manage Local Storage —> minimum 2: Setting / Advanced / Automatic Media Download / In private chats / groups / channels —> optionally you can turn that off
Ok, and now? How can i do that? The answer is pretty simply. It depends which MacOS app are you using. If you are using Telegram for MacOS (Stable or Beta Apple CPU compatible or not), you need to change the following option: Setting / Data and Storage / Storage Usage —> Maximum cache size to the minimum and auto remove after 1 day for all three options.
Yes, we know you want to know what is the most important thing Telegram Freaks need to do, but sorry, you need to wait. Let we check what is the second most important thing you can do on Telegram: for sure be able to manage storage in proper way!
Channel photo updated
Channel created
Showing the 11 most recent of 11 posts we hold for @KingTelegramUser. 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.
Named by 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“The most important things Telegram Freaks need to do” (@KingTelegramUser), 7 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/KingTelegramUser.
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.