Telegram RegisterThe public register of Telegram
Telegram profile photo for бункер дайки

Channel

бункер дайки

@maxdaykaa

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

10,532subscribers

+1,886 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001742022138
TypeChannel
Username@maxdaykaa
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/maxdaykaa

Growth

8,57710,6199,5986 August 2026 — 8,646 subscribers6 August 2026 — 8,646 subscribers7 August 2026 — 8,642 subscribers10 August 2026 — 8,628 subscribers13 August 2026 — 8,620 subscribers16 August 2026 — 8,609 subscribers19 August 2026 — 8,601 subscribers23 August 2026 — 8,577 subscribers25 August 2026 — 9,175 subscribers28 August 2026 — 10,619 subscribers29 August 2026 — 10,532 subscribers10,5326 August 202629 August 2026
11 measurements spanning 23 days, net +1,886. 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 8,271–10,925 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 14:5410,532-87
28 Aug 2026, 11:3710,619+1,444
25 Aug 2026, 15:439,175+598
23 Aug 2026, 02:158,577-24
19 Aug 2026, 23:028,601-8
16 Aug 2026, 22:088,609-11
13 Aug 2026, 15:068,620-8
10 Aug 2026, 12:218,628-14
7 Aug 2026, 14:188,642-4
6 Aug 2026, 17:158,646no change
6 Aug 2026, 16:418,646first reading

Engagement

61 posts held, back to 23 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 30 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.7%
avg views ÷ 10,532 subscribers
Avg views / post
2,290
42 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
42
of 61 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 27 August 2026
Posts held61 (23 April 202627 August 2026)
Views total96,160
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 13:17 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

Video runtime
3m 14s
Average length
1m 05s

Measured directly from 3 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.

Recent posts

27 Aug 2026, 17:10 UTC≈2,300 viewsread 28 August 2026

тильт продолжается, из-за 1 ошибки сделал 5 шагов назад...

26 Aug 2026, 19:18 UTC≈2,390 viewsread 27 August 2026

ывафызвазфыкезйцузеквыаффывафываывал из +2к в -6500

26 Aug 2026, 09:19 UTC≈2,100 viewsread 26 August 2026

ничего страшного, проигрыши случаются, главное не опускать руки и продолжать работать холодной головой!☑️

25 Aug 2026, 15:37 UTC≈4,070 viewsread 29 August 2026

айфон 17 про макс? те кто не знают 💀 https://t.me/maxdayka/s/48

25 Aug 2026, 05:10 UTC≈2,220 viewsread 25 August 2026

всем хай, с розыгрыша тоже хай, стрим к 21 думаю, весь день на трек ивенте от бмв, может подсниму чет в лайв канал t.me/nemaxdayka

24 Aug 2026, 21:00 UTC≈2,140 viewsread 28 August 2026
Forwarded from @stas_refundPhoto

МЕГА РОЗЫГРЫШ 1.500$ 🖤 15 челиков получат по 100$ 💲 Для участия нужно быть подписанным на эти каналы: ⭐ https://t.me/stas_refund ⭐ https://t.me/maxdaykaa ⭐https://t.me/ludkafm ⭐ https://t.me/hisokah1 ⭐ https://t.me/yafrzd Итоги розыгрыша через 72 часа

24 Aug 2026, 14:30 UTC≈3,020 viewsread 28 August 2026
Photo

Микрозанос ➡️ Регистрация в EPICSTAR Код: DAYKA ⭐️

22 Aug 2026, 18:00 UTC≈1,780 viewsread 22 August 2026
Photo

🔴 kick.com/maxdayka 🔴 СУББОТА, ПИВО, КАЛЬЯН ➡️ Регистрация в EPICSTAR Код: DAYKA ⭐️

22 Aug 2026, 17:38 UTC≈1,900 viewsread 22 August 2026
Photo

21:00, походу сегодня все деньги проебу (это все вороны)

19 Aug 2026, 17:21 UTC≈2,010 viewsread 20 August 2026
Photo

микро камбекич ➡️ Регистрация в EPICSTAR Код: DAYKA ⭐️

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

Posts edited after publishing

@maxdaykaa edited 1 post 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.

First edit seen
24 August 2026
Most recent edit
24 August 2026

Citation-graph rank

Citation-graph rank — 623,969 of 1,626,884entries 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

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.

Mentions

Named by 12 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.

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

“бункер дайки” (@maxdaykaa), 10,532 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/maxdaykaa.

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.