Telegram RegisterThe public register of Telegram
Telegram profile photo for mil3s

Channel

mil3s

@mil3spage

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-1002506717528
TypeChannel
Username@mil3spage
DescriptionОфициальный пейдж игрока "mil3s" Здесь будут выкладываться:результаты игр,моменты из игр(по возможности) и мои достижения в игре Команды в которых я играл: xLegacy renicolous royal rabbits 5k7 br9y LoPai CYBERZERO M08 L1k9
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/mil3spage

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:4616no change
7 Aug 2026, 17:0516first reading

Engagement

17 posts held, back to 16 August 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 27 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
89
Videos
5
Links
2

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. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

27 Aug 2025, 19:06 UTC60 viewsread 11 August 2026
Forwarded from @mil3sik

+2 в мм калибровка От вас феникс (8 с) Лега,дабл элита-дабл лега(9 сезон) Писать в ЛС @mili3s

27 Aug 2025, 15:17 UTC66 viewsread 11 August 2026

Талант 4 на 11 в конце не выдержал напора хуев ему в очко и начал говорить что я долбоеб,но позже переобулся и сказал что я крутой

26 Aug 2025, 14:53 UTC53 viewsread 11 August 2026
Forwarded from @MiKEboiTiers12

❗Поздравляю mil3s, вы официально T2 по мнению - MiKEboi tiers Удачи! За повышением тира писать в @MiKEboi78D

26 Aug 2025, 07:44 UTC46 viewsread 11 August 2026
Forwarded from @acermup

" mil3s"поздравляю ваш тир "Т1"за тиром писать @ACER1377 Тгк @acerctanok

25 Aug 2025, 06:28 UTC46 viewsread 11 August 2026
Forwarded from @mil3sik

Вторую S добавил думает я не замечу

25 Aug 2025, 06:28 UTC45 views0 reactionsread 11 August 2026
Forwarded from @mil3sik

Признавайтесь кто ник украл

24 Aug 2025, 19:25 UTC422 viewsread 11 August 2026

FFT 8 season MM: phoenix Напы:gold 1 Дуэли:gold 1 9 season MM: elite Напы: legend Дуэли: champion Актив: 13:00-18:00 (до начала учебного года) 18:00(19:00)-00:00 (после начала учебного года Роль: опенфрагер/рифла/люркер/снайпер Девайс: Oneplus 13 Играю по пл/тг войсу Резы есть От вас: Праки/туры/разборы Входить в мой график Дружелюбный стак ± не нн Актив Стак от г4-фениксов+(8 сезон) Элиты-леги(9 сезон) ЛС: @mili3s

20 Aug 2025, 14:53 UTC117 viewsread 11 August 2026

Чтобы вы понимали,переписка сверху это я делал разбор дюны на а плент,типо как залезать флешки смок и т.д,ТАК ОНИ БЛЯТЬ ТОЛЬКО НА А ХОДИЛИ,Я КОЛЮ ЗА ЭТОГО НЕДО КЕПА ЧТОБЫ ВЫ ПОНИМАЛИ,КОРОЧЕ Я ВАХУЕ,ДУИАЛ НОРМ ТИМА,ОКАЗАЛАСЬ ХУЙНЯ,И ДА У НИХ В НАБОРЕ ИГРОКОВ НАПИСАНО РАЗБОРЫ/ПРАКИ/ТУРЫ/БК,получается пиздаболы?

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

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

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.

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.

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

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.