Ночная подборочка Спать, режим
custom 5258249733742296479176custom 536652444193524879859custom 546965784664161032717custom 52852213037274626527

Channel
@why4ch
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,042,455subscribers
-23,967 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001967505770 |
|---|---|
| Type | Channel |
| Username | @why4ch |
| Description | Единственный и неповторимый 4ch Реклама: @adv4ch РКН: https://clck.ru/3FiYXP |
| Created | 18 March 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 24 September 2026 |
| On Telegram | t.me/why4ch |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 67% 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 why it has no browse page of its own yet.
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.
On 15 of the 411 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0152 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /3469819 Sept 2026, 08:33 UTC | 31 minutes | 11,900 → 14,400at least +2,400 | 374 → 379at most +6 | +36.4 |
| /3469819 Sept 2026, 08:33 UTC | 35 minutes | 16,500 → 19,600at least +3,000 | 382 → 385at most +4 | +45.5 |
| /3469819 Sept 2026, 08:33 UTC | 5 days | 27,800 → 44,200at least +16,300 | 393 → 407at most +15 | +247.2 |
| /343278 Sept 2026, 08:33 UTC | 30 minutes | 31,100 → 36,700at least +5,500 | 345 → 360at most +16 | +83.4 |
| /343278 Sept 2026, 08:33 UTC | 35 minutes | 36,700 → 45,700at least +8,900 | 360 → 379at most +20 | +135.0 |
| /3466618 Sept 2026, 07:10 UTC | 34 minutes | 16,800 → 19,800at least +2,900 | 418 → 425at most +8 | +44.0 |
| /3466618 Sept 2026, 07:10 UTC | 5 days | 41,600 → 48,200at least +6,500 | 457 → 463at most +7 | +98.6 |
| /3487025 Sept 2026, 13:34 UTC | 35 minutes | 15,600 → 19,600at least +3,900 | 428 → 436at most +9 | +59.2 |
| /3487025 Sept 2026, 13:34 UTC | 9.4 hours | 31,900 → 37,300at least +5,300 | 452 → 460at most +9 | +80.4 |
| /3490026 Sept 2026, 09:33 UTC | 35 minutes | 13,000 → 16,000at least +2,900 | 271 → 279at most +9 | +44.0 |
| /3490026 Sept 2026, 09:33 UTC | 35 minutes | 16,000 → 19,700at least +3,600 | 279 → 284at most +6 | +54.6 |
| /341372 Sept 2026, 04:41 UTC | 35 minutes | 24,800 → 28,700at least +3,800 | 287 → 298at most +12 | +57.6 |
| /342244 Sept 2026, 17:52 UTC | 31 minutes | 38,300 → 45,100at least +6,700 | 386 → 409at most +24 | +101.6 |
| /3452514 Sept 2026, 04:33 UTC | 8 days | 59,200 → 69,300at least +10,000 | 458 → 479at most +22 | +151.7 |
| /3455914 Sept 2026, 19:10 UTC | 7 days | 56,700 → 68,600at least +11,800 | 586 → 613at most +28 | +179.0 |
| /3456615 Sept 2026, 04:47 UTC | 7 days | 64,000 → 75,400at least +11,300 | 492 → 519at most +28 | +171.4 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 28 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Sept 2026, 23:17 | 1,042,455 | -2,992 |
| 18 Sept 2026, 19:55 | 1,045,447 | -1,121 |
| 16 Sept 2026, 11:40 | 1,046,568 | -859 |
| 14 Sept 2026, 15:57 | 1,047,427 | -788 |
| 13 Sept 2026, 03:39 | 1,048,215 | -877 |
| 11 Sept 2026, 07:55 | 1,049,092 | -1,328 |
| 8 Sept 2026, 10:56 | 1,050,420 | -1,525 |
| 5 Sept 2026, 03:17 | 1,051,945 | -677 |
| 3 Sept 2026, 09:16 | 1,052,622 | -580 |
| 2 Sept 2026, 01:17 | 1,053,202 | -500 |
| 1 Sept 2026, 01:49 | 1,053,702 | -498 |
| 31 Aug 2026, 02:13 | 1,054,200 | -464 |
| 30 Aug 2026, 03:25 | 1,054,664 | -393 |
| 29 Aug 2026, 05:26 | 1,055,057 | -361 |
| 28 Aug 2026, 08:12 | 1,055,418 | -487 |
| 27 Aug 2026, 06:11 | 1,055,905 | -474 |
| 26 Aug 2026, 06:12 | 1,056,379 | -438 |
| 25 Aug 2026, 09:43 | 1,056,817 | -575 |
| 24 Aug 2026, 08:12 | 1,057,392 | -804 |
| 22 Aug 2026, 19:26 | 1,058,196 | first reading |
3,877 posts held, back to 25 January 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 391 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 28 September 2026 |
|---|---|
| Posts held | 3,877 (25 January 2026 – 28 September 2026) |
| Views total | 26,352,900 |
| Reactions total | 396,671 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 02:00 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.
Lifetime counters from Telegram’s own channel header, read 28 September 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.
Measured directly from 395 videos 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 411 of this channel’s own posts over the last 30 days (17 of the 24-hour readings behind this are interpolated, not measured directly): across 395 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.9 hours of being posted; a typical post has already reached 32.1% of its 24-hour view count within the first hour, and 72.1% within the first six; the median 24-hour reach across those posts is 43,400 views — 4.16% of this channel’s own subscriber count (90th percentile 49,900).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /3496528 Sept 2026, 19:40 UTC | 1325 minutes – 6.3 hours old | 16,600 views ~259 reactions | 60 minutes: 9,891 interp. → 3.0 hours: 14,000 → 6.0 hours: 16,100still climbing at last reading | not yet at 24h | 42 minutesprovisional — final view count still climbing |
| /3496428 Sept 2026, 18:38 UTC | 1522 minutes – 7.4 hours old | 22,100 views ~510 reactions | 60 minutes: 11,723 interp. → 3.0 hours: 18,800 → 6.0 hours: 21,300still climbing at last reading | not yet at 24h | 54 minutesprovisional — final view count still climbing |
| /3496328 Sept 2026, 17:00 UTC | 1820 minutes – 9.0 hours old | 26,200 views ~524 reactions | 60 minutes: 11,505 interp. → 3.0 hours: 21,500 → 6.0 hours: 24,700still climbing at last reading | not yet at 24h | 80 minutesprovisional — final view count still climbing |
| /3496228 Sept 2026, 15:42 UTC | 2028 minutes – 10 hours old | 30,700 views ~816 reactions | 60 minutes: 12,700 → 3.0 hours: 22,422 interp. → 6.0 hours: 28,800still climbing at last reading | not yet at 24h | 83 minutesprovisional — final view count still climbing |
| /3496128 Sept 2026, 14:14 UTC | 2316 minutes – 12 hours old | 35,900 views ~1,186 reactions | 60 minutes: 16,377 interp. → 3.0 hours: 27,100 → 6.0 hours: 33,000 → 12 hours: 35,900still climbing at last reading | not yet at 24h | 75 minutesprovisional — final view count still climbing |
| /3496028 Sept 2026, 12:48 UTC | 2538 minutes – 13 hours old | 39,700 views ~1,124 reactions | 60 minutes: 15,699 interp. → 3.0 hours: 28,100 → 6.0 hours: 36,000 → 12 hours: 39,400still climbing at last reading | not yet at 24h | 88 minutesprovisional — final view count still climbing |
| /3495928 Sept 2026, 12:05 UTC | 2630 minutes – 14 hours old | 36,700 views ~611 reactions | 60 minutes: 14,411 interp. → 3.0 hours: 26,000 → 6.0 hours: 32,000 → 12 hours: 36,200still climbing at last reading | not yet at 24h | 86 minutesprovisional — final view count still climbing |
| /3495828 Sept 2026, 11:10 UTC | 2821 minutes – 15 hours old | 98,100 views ~872 reactions | 60 minutes: 27,523 interp. → 3.0 hours: 53,994 interp. → 6.0 hours: 73,900 → 12 hours: 94,800still climbing at last reading | not yet at 24h | 2.5 hoursprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
744,939 reactions across 902 posts, in 8 distinct kinds. The most used accounts for 21.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5467690236223967649 | 159,300 | 21.4% | |
| custom 5267026130044488516 | 154,126 | 20.7% | |
| custom 5469657846641610327 | 137,027 | 18.4% | |
| custom 5467713446227234408 | 98,902 | 13.3% | |
| custom 5366524441935248798 | 71,892 | 9.65% | |
| custom 5258249733742296479 | 65,877 | 8.84% | |
| custom 5285221303727462652 | 47,032 | 6.31% | |
| custom 5460704463327074557 | 10,783 | 1.45% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 999 of the 1,000 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 835,251 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 30 July 2026 to 28 September 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnje6zAR1 | 1 | 21 August 2026 | 21 August 2026 |
| 2SDnjezyn6f | 1 | 21 August 2026 | 21 August 2026 |
| 2Vtzqx3wzXd | 1 | 25 August 2026 | 25 August 2026 |
| 2Vtzqx5BG3c | 1 | 5 August 2026 | 5 August 2026 |
| CQH36pWzJqNJuck8RJrAbvSPBTunxz3FGKuZpYamMBxDLu | 1 | 18 August 2026 | 18 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 30 July 2026 to 28 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Ночная подборочка Спать, режим
custom 5258249733742296479176custom 536652444193524879859custom 546965784664161032717custom 52852213037274626527
Пожалуй, нет лучшего способа проиллюстрировать различия между зумерами и миллениалами 😁 4ch
custom 5366524441935248798367custom 528522130372746265276custom 546965784664161032745custom 525824973374229647922
Курсы в современных условиях кризиса на рынке труда выглядят как-то так 😁 4ch
custom 5258249733742296479430custom 536652444193524879849custom 528522130372746265229custom 546965784664161032716
То же самое происходит, когда ты идёшь в спортзал 😁 4ch
custom 5258249733742296479621custom 5469657846641610327101custom 536652444193524879871custom 528522130372746265223
Том Круз завирусился после того, как решил помочь грустной сотруднице на съёмках Актёр заметил девушку, которая выглядела расстроенной, и решил проверить, всё ли с ней в порядке. Оказалось, она просто залипла в ленту соцсетей. 4ch
custom 5258249733742296479900custom 5366524441935248798182custom 528522130372746265294custom 546965784664161032710
Школьник с помощью ИИ взломал внутреннюю базу Microsoft — и получил $5 000 16-летний школьник создал ИИ-бота, который 10 дней методично исследовал авторизацию внутренней аналитической системы Titan. Бот нашёл уязвимость: можно было подделать токен, представиться администратором и получить доступ к данным. Всего под угрозой оказались 17 баз с суммарно 17,3 трлн строк. Парень не стал выкачивать всё, а сообщил о дыре M…
custom 5469657846641610327859custom 5285221303727462652163custom 536652444193524879877custom 525824973374229647925
Ну мы 😁 4ch для стариков: Ларпить — выдавать себя за кого-то другого в интернете, изображать эксперта
custom 5258249733742296479473custom 546965784664161032781custom 536652444193524879846custom 528522130372746265211
Вчера состоялся самый легендарный футбольный матч❗️4ch
custom 5258249733742296479687custom 546965784664161032787custom 536652444193524879863custom 528522130372746265235
Как уход с работы и исчезновение навсегда смотрят на тебя в 10 утра в случайный понедельник 4ch:
custom 5366524441935248798578custom 525824973374229647998custom 546965784664161032743custom 528522130372746265215
Айтишники стали непривлекательны для женщин, а работа в бигтехе стала помехой для свиданий в США По данным Wired, айтишники из крупных техкомпаний всё чаще сталкиваются с неприязнью на свиданиях и даже скрывают работодателя в анкетах. Сотрудника Palantir девушки называли «дьяволом», работника Tesla расспрашивали о политических взглядах из-за Маска. Big Tech всё чаще ассоциируется с ИИ, слежкой и массовыми увольнения…
custom 5285221303727462652397custom 546965784664161032768custom 536652444193524879832custom 52582497337422964799
Что Пуш ПРЯЧЕТ в своём кейсе? 😂 Посмотрите, это же кейс с деньгами для Альфа-Вклада — со ставкой 14,5% годовых. Такая ставка доступна всем новым клиентам и Пушам. А ещё тем, кто не открывал вклады в банке последний год. Редактор канала: вкладывается в ваше настроение своими шутками 🤔 @alfa_vygodno
custom 5366524441935248798320custom 546965784664161032783custom 52582497337422964792custom 52852213037274626522
Вы много раз его слышали, но могли ни разу не видеть Это древесный сверчок: он поднимает крылья и поёт, чтобы позвать самку. По песне она понимает, где он и насколько он хорош. 4ch
custom 5258249733742296479490custom 5366524441935248798111custom 546965784664161032740custom 528522130372746265217
Showing the 12 most recent of 3,877 posts we hold for @why4ch. 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.
@why4ch edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 46 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1,063 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
69 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“4ch” (@why4ch), 1,042,455 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/why4ch.
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.