Telegram RegisterThe public register of Telegram

Channel

Recap Time

@RecapTime

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

16subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001443574769
TypeChannel
Username@RecapTime
DescriptionPost-battle summaries in @chtwrs, forwards from different chats we liked, FAQs from our handbook's Community Hub, etc. Also for archives in our chats. Discussion: @RecapTime_LiveChat Main Channel: @UpdatesFromThePinsTeam Inquiries: @AJHalili2006
Created24 August 2019measured — cross-checked against a third-party dataset (TGDataset)
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/RecapTime

Growth

167 August 2026 — 16 subscribers11 August 2026 — 16 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 21:1616no change
7 Aug 2026, 23:1216first reading

Engagement

20 posts held, back to 8 June 2022the 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.

ERR · 30 days
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 July 2026
Posts held20 (8 June 202215 July 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 21:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
446
Videos
21
Links
1,690

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

15 Jul 2026, 08:22 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

6 Jul 2026, 09:01 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

26 Jun 2026, 20:11 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

18 May 2023, 21:43 UTC543 viewsread 11 August 2026

@Kuys_potpot: obviously redoing this due to account recovery process behind the scenes

Signed Social Media Reposter Bot

18 May 2023, 21:43 UTC568 viewsread 11 August 2026

Verifying myself: I am recaptimesquad on https://t.co/LKO5jpXqxP. TNoE3pL4hs4w_CX9ThqPpxrkk0I842ZmoO-Z / https://t.co/PQgBHBPcx9

Signed Social Media Reposter Bot

27 Oct 2022, 17:05 UTC599 viewsread 11 August 2026

🔁 RT @kingbdogz: Btw did you know JAPPA's name is actually Jesper? People often get it wrong by spelling it "Jasper", but that's incorrect.

Signed Social Media Reposter Bot

1 Aug 2022, 14:37 UTC439 viewsread 11 August 2026

🔁 RT @ComUpdatesRadio: #crosspost #feedmeta: @Kuys_Potpot speaking here. The Updates Radio feed is currently in the process of documenting hashtags used in update posts and even quoting some posts between platforms. If you want to be featured here, feel free to contact me through DMs.

Signed Social Media Reposter Bot

26 Jul 2022, 14:56 UTC291 viewsread 11 August 2026

@Kuys_Potpot, observing outside the fandom: The what. *triggers emergency meeting mentally* https://t.co/hiT4TiBLUg

Signed Social Media Reposter Bot

10 Jul 2022, 07:39 UTC253 viewsread 11 August 2026

We would not rather play that all loud. https://t.co/KrsimKEBM3

Signed Social Media Reposter Bot

10 Jul 2022, 07:39 UTC140 viewsread 11 August 2026

We guess we should watch it to see the chaos it caused, probably. - ajhalili2006 https://t.co/F1zkeXCs12

Signed Social Media Reposter Bot

Showing the 12 most recent of 20 posts we hold for @RecapTime. 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.

Citation-graph rank

Citation-graph rank — 919,158 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — 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.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Recap Time” (@RecapTime), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/RecapTime.

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.