Posted without readable text
custom 546965784664161032776custom 528522130372746265227custom 525824973374229647913custom 53665244419352487988

Channel
@why4ch
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,019,801subscribers
-46,621 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 | 14 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 14 November 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 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 12 other registered channels. 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 |
|---|---|---|---|
| @why4ch/36119 · this entry2 Nov 2026, 16:16 UTC | @ORGINALDANKEZT1/752863 Nov 2026, 18:03 UTC | 1.00 | 26 hours |
| @ORGINALDANKEZT1/740987 Sept 2026, 11:39 UTC | @why4ch/34326 · this entry8 Sept 2026, 07:59 UTC | 0.99 | 20 hours |
| @ORGINALDANKEZT1/7519630 Oct 2026, 06:18 UTC | @why4ch/36024 · this entry30 Oct 2026, 16:33 UTC | 0.99 | 10 hours |
| @ORGINALDANKEZT1/7543510 Nov 2026, 17:03 UTC | @why4ch/36351 · this entry10 Nov 2026, 18:40 UTC | 0.99 | 1.6 hours |
| @ORGINALDANKEZT1/7487815 Oct 2026, 07:59 UTC | @why4ch/35519 · this entry15 Oct 2026, 08:30 UTC | 0.98 | 31 minutes |
| @ORGINALDANKEZT1/7513828 Oct 2026, 09:08 UTC | @why4ch/35938 · this entry28 Oct 2026, 10:26 UTC | 0.98 | 77 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ORGINALDANKEZT1 | 46 (8/8 hand-verifiable sample passed) | 0.98 | 1.5 hours | @ORGINALDANKEZT1 (33–13) |
| @unohp | 24 (8/8 hand-verifiable sample passed) | 1.00 | 63 minutes | this entry (24–0) |
| @zhiga | 20 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | this entry (20–0) |
| @Scienceg | 15 (8/8 hand-verifiable sample passed) | 0.98 | 1.5 hours | @Scienceg (11–4) |
| @cbpub | 14 (8/8 hand-verifiable sample passed) | 0.98 | 3.1 hours | even |
| @politika_video_novosti | 10 (8/8 hand-verifiable sample passed) | 0.97 | 1.7 hours | this entry (6–4) |
| @catboywhite | 9 (8/8 hand-verifiable sample passed) | 0.97 | 50 minutes | @catboywhite (5–4) |
| @telegrachan | 9 (8/8 hand-verifiable sample passed) | 0.98 | 16 minutes | this entry (6–3) |
| @zloyizhevchanin | 8 (8/8 hand-verifiable sample passed) | 0.98 | 21 hours | this entry (8–0) |
| @retra | 5 (5/5 hand-verifiable sample passed) | 0.92 | 2.3 hours | @retra (5–0) |
| @alfabank | 12 (8/8 hand-verifiable sample passed) | 1.00 | 16 hours | @alfabank (12–0) |
| @alfa_vygodno | 5 (5/5 hand-verifiable sample passed) | 1.00 | 14 hours | @alfa_vygodno (4–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. 73 of the 75 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 2,295 comparable posts for this entry, running 25 January 2026 to 14 November 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 14 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 03:16 | 1,019,801 | -1,211 |
| 11 Nov 2026, 06:40 | 1,021,012 | -659 |
| 9 Nov 2026, 14:07 | 1,021,671 | -593 |
| 8 Nov 2026, 07:47 | 1,022,264 | -484 |
| 7 Nov 2026, 00:36 | 1,022,748 | -341 |
| 6 Nov 2026, 02:57 | 1,023,089 | -448 |
| 5 Nov 2026, 05:19 | 1,023,537 | -352 |
| 4 Nov 2026, 03:19 | 1,023,889 | -429 |
| 3 Nov 2026, 04:37 | 1,024,318 | -414 |
| 2 Nov 2026, 05:11 | 1,024,732 | -388 |
| 1 Nov 2026, 05:58 | 1,025,120 | -389 |
| 31 Oct 2026, 02:18 | 1,025,509 | -342 |
| 30 Oct 2026, 02:29 | 1,025,851 | -513 |
| 28 Oct 2026, 23:45 | 1,026,364 | -428 |
| 27 Oct 2026, 23:16 | 1,026,792 | -431 |
| 26 Oct 2026, 20:49 | 1,027,223 | -362 |
| 25 Oct 2026, 21:37 | 1,027,585 | -364 |
| 25 Oct 2026, 00:50 | 1,027,949 | -302 |
| 23 Oct 2026, 22:29 | 1,028,251 | -576 |
| 22 Oct 2026, 20:39 | 1,028,827 | first reading |
4,599 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 485 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. It is computed over the 453 of 454 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 4,599 (25 January 2026 – 14 November 2026) |
| Views total | 15,972,998 |
| Reactions total | 255,882 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 15:26 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 14 November 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 406 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 394 of this channel’s own posts over the last 30 days (15 of the 24-hour readings behind this are interpolated, not measured directly): across 365 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 31.5% 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 42,900 views — 4.15% of this channel’s own subscriber count (90th percentile 49,900).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /3545413 Oct 2026, 19:40 UTC | 1055 minutes – 6.3 hours old | 18,400 views ~287 reactions | 60 minutes: 11,141 interp. → 3.0 hours: 15,600 → 6.0 hours: 17,900still climbing at last reading | not yet at 24h | 55 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /3545313 Oct 2026, 17:43 UTC | 1412 minutes – 8.3 hours old | 30,800 views ~884 reactions | 60 minutes: 16,200 interp. → 3.0 hours: 25,700 → 6.0 hours: 29,400still climbing at last reading | not yet at 24h | 54 minutesprovisional — final view count still climbing |
| /3545213 Oct 2026, 15:43 UTC | 1718 minutes – 10 hours old | 33,800 views ~573 reactions | 60 minutes: 12,102 interp. → 3.0 hours: 24,600 → 6.0 hours: 31,729 interp.still climbing at last reading | not yet at 24h | 1.8 hoursprovisional — final view count still climbing |
| /3545113 Oct 2026, 14:54 UTC | 192 minutes – 11 hours old | 34,900 views ~671 reactions | 60 minutes: 14,109 interp. → 3.0 hours: 23,800 → 6.0 hours: 32,800still climbing at last reading | not yet at 24h | 1.5 hoursprovisional — final view count still climbing |
| /3545013 Oct 2026, 13:56 UTC | 2029 minutes – 12 hours old | 57,800 views ~700 reactions | 60 minutes: 23,800 → 3.0 hours: 35,756 interp. → 6.0 hours: 50,500 → 12 hours: 57,800still climbing at last reading | not yet at 24h | 1.6 hoursprovisional — final view count still climbing |
| /3544913 Oct 2026, 13:44 UTC | 2042 minutes – 12 hours old | 41,600 views ~792 reactions | 60 minutes: 21,897 interp. → 3.0 hours: 31,000 → 6.0 hours: 38,200 → 12 hours: 41,600still climbing at last reading | not yet at 24h | 53 minutesprovisional — final view count still climbing |
| /3544813 Oct 2026, 13:21 UTC | 2114 minutes – 13 hours old | 38,200 views ~585 reactions | 60 minutes: 19,983 interp. → 3.0 hours: 29,352 interp. → 6.0 hours: 34,700 → 12 hours: 38,000still climbing at last reading | not yet at 24h | 57 minutesprovisional — final view count still climbing |
| /3544713 Oct 2026, 12:36 UTC | 2224 minutes – 13 hours old | 45,300 views ~1,350 reactions | 60 minutes: 21,900 → 3.0 hours: 35,400 → 6.0 hours: 41,400 → 12 hours: 45,000still climbing at last reading | not yet at 24h | 63 minutesprovisional — 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.
675,200 reactions across 998 posts, in 5 distinct kinds. The most used accounts for 33.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366524441935248798 | 226,182 | 33.5% | |
| custom 5258249733742296479 | 181,426 | 26.9% | |
| custom 5285221303727462652 | 114,512 | 17.0% | |
| custom 5469657846641610327 | 96,234 | 14.3% | |
| 🫡 | 56,846 | 8.42% |
Custom emoji. 4 of the rows above are 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 998 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 675,200 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 10 September 2026 to 14 November 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqwyPvN2 | 1 | 3 November 2026 | 3 November 2026 |
| 2W5zFG3i7w7 | 1 | 15 October 2026 | 15 October 2026 |
| 2W5zFG6b4jK | 1 | 20 October 2026 | 20 October 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 10 September 2026 to 14 November 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.
Telegram’s own ‘edited’ marker: 21 of 454 posts held from the last 30 days (4.63%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Posted without readable text
custom 546965784664161032776custom 528522130372746265227custom 525824973374229647913custom 53665244419352487988
Posted without readable text
custom 5366524441935248798203🫡34custom 528522130372746265220custom 54696578466416103274custom 52582497337422964793
Какой-то чувак увидел оленя, переходящего дорогу посреди улицы, крикнул ему, чтобы тот использовал пешеходный переход. И олень пошёл и воспользовался им 🙂 Вежливая зверюга❗️4ch
custom 5366524441935248798647custom 525824973374229647995custom 528522130372746265238custom 546965784664161032712🫡10
Девушка купила тарелку в надежде на милые фотки с кроликом, но в итоге это выглядит так, будто он насрал ей полную тарелку 🙄 4ch
🫡367custom 546965784664161032766custom 536652444193524879858custom 525824973374229647916custom 52852213037274626529
В ноябре даже нет второй половины дня. Ты пообедал — и уже почти завтра 😮💨 4ch
custom 5469657846641610327418custom 536652444193524879870custom 525824973374229647924custom 528522130372746265217🫡16
Нейросетям раздали по $10 000 и отправили делать ставки на спорт 11 топовых ИИ-моделей получили доступ к букмекерским линиям и теперь самостоятельно выбирают матчи, рассчитывают ставки и пытаются заработать За 30 дней Grok вырвался на первое место, а Gemini и DeepSeek уже ушли в минус. Результаты всех моделей показывают в открытом рейтинге Скайнет нашёл себе подработку. 4ch
custom 5366524441935248798250custom 525824973374229647947custom 546965784664161032727🫡10custom 52852213037274626526
Надо почаще так собираться, пацаны 😳 4ch
custom 5469657846641610327347custom 536652444193524879892custom 528522130372746265236custom 525824973374229647919
Сегодня отмечается День расслабленности и беззаботности. 4ch
custom 5258249733742296479342custom 546965784664161032757🫡28custom 536652444193524879823custom 52852213037274626527
Утренняя подборочка
custom 5366524441935248798232custom 525824973374229647935custom 546965784664161032714🫡8custom 52852213037274626524
Восстание машин отменяется: работяги в США научились прогонять беспилотные такси табличкой «Стоп» Достаточно показать знак в камеру Waymo: машина сдаёт назад, а потом разворачивается и уезжает Человечество спасено. 4ch
custom 5366524441935248798561custom 525824973374229647981custom 528522130372746265234custom 546965784664161032714🫡5
Это же буквально я ✋ Видео скачано через нашего бота
custom 5285221303727462652337custom 536652444193524879874🫡27custom 525824973374229647910custom 54696578466416103279
Ночная подборочка Выходные, не спим
🫡255custom 536652444193524879883custom 525824973374229647919custom 546965784664161032713custom 52852213037274626529
Showing the 12 most recent of 4,599 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 7 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.
We recorded 1 post on @why4ch as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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 48 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,084 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“4ch” (@why4ch), 1,019,801 subscribers as measured 14 November 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.