Telegram RegisterThe public register of Telegram

Channel

❯❯ ᑕᕼɆᗷᑌ'S ꕤ ᑭØᖇTᖴØᒪIØ !!

@chebusport

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

6subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002431081773
TypeChannel
Username@chebusport
CreatedBetween 1 September 2024 and 6 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/chebusport

Growth

612 Aug 2026, 20:15 — 6 subscribers12 Aug 2026, 22:17 — 6 subscribers12 Aug 2026, 20:1512 Aug 2026, 22:17
2 measurements taken within a single day. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:176no change
12 Aug 2026, 20:156first reading

Engagement

20 posts held, back to 6 February 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 20 posts for this entry, the most recent from 13 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
27
Videos
1
Links
6

Lifetime counters from Telegram’s own channel header, read 12 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

13 Jun 2025, 12:35 UTC69 viewsread 12 August 2026
Photo

. ꒱ : " Ꮺ 🔤авигация . . ! ˚ ⌗🪽🪽 .┊. 🌟🌟🌟🌟 🌹 ೃ ‹ ‹ — личные сообщения; . . ˚ ꒰ 💋 . . — анонимные; . જ правила; 📡 знакомство; ‹ ‹ — шаблон для вп. 🎭 . ꒱ ˚ 🌟┈┈┈┈🌟🌟┈┈┈┈🌟 ˚ . ִׄ #арт 🎲 #эдит ⌨️ #мем . ִׄ ‹ ‹ . 𓂃 #прохождения 🤍 ˚ 🌟┈┈┈┈🌟🌟┈┈┈┈🌟 ˚ . seven hearts stories ➵ . . . . ◯⃘ ֺ︩

7 Jun 2025, 08:17 UTC62 viewsread 12 August 2026
Photo

˙ . 🌟𝘢𝘷𝘪𝘨𝘢𝘵𝘪𝘰𝘯 ˙ ♱ . ( 🌟 ) ✮ ° 🤩 ➿➿➿➿➿➿➿➿➿ 🤩 ⊹ っ `᭡᭡ 🌟𝘥𝘮𝘪𝘯𝘪𝘴𝘵𝘳𝘢𝘵𝘪𝘰𝘯 𝒢 ⟡ ५🤩 🌟𝘯𝘰𝘯 ꒱ ⊹ っ 🤩 -- (!) ୨୨ ۫ 🌟۫۫ ┈۫ 🌟 ۫۫ 🌟 ۫۫ 🌟 ┈۫ 🌟 ۫ ୧୧ ⟡ 🌟𝘢𝘵𝘦𝘯𝘵 ┊ 🤩 。 ᓚᘏᗢ 。 (!) ˙. 🤩 :: 🌟𝘯𝘪𝘵𝘪𝘢𝘭𝘴 𝒢 ๑˚ ⟡ 🤩 ⟡ ˙. 🤩 。 ┊🌟𝘢𝘮𝘪𝘭𝘺 ˙. ୨୨ ۫ 🌟۫۫ ┈۫ 🌟 ۫۫ 🌟 ۫۫ 🌟 ┈۫ 🌟 ۫ ୧୧ ⟡ 🤩 ˙. 🌟𝘪𝘴𝘵 𝘰𝘧 𝘳𝘰𝘭𝘦𝘴 𝒢 🤩 ५ 🤩 🌟𝘩𝘢𝘵 𝘳𝘶𝘭𝘦𝘴 ˙. ⟡ 🌟𝘪𝘬𝘵𝘰𝘬 ⊹ ୨୨ 🌟 ┈ 🌟 🌟 🌟 ┈ 🌟 ୧୧ — #𝗞𝗔𝗘𝗡ʳᵖ

7 Jun 2025, 08:16 UTC60 viewsread 12 August 2026
Photo

ㅤ ┄ 🤍𝒂𝒗𝒊𝒈𝒂𝒕𝒊𝒐𝒏 . . . 💛 !! . 🤩🌟🌟🌟 🤩🌟🌟🌟 🤩. ❯❯ . 🤩 𝓟𝒂𝒕𝒆𝒏𝒕 ୭ 𝓘𝒏𝒊𝒕𝒊𝒂𝒍𝒔 . ୭ 𝓒𝒉𝒂𝒕 𝒓𝒖𝒍𝒆𝒔 .〢 🤩 .🤩 𝓐𝒅𝒎𝒊𝒏𝒔 ◠ ˖ ◌ . ◠ ˖ ◌ . ୭ 𝓤𝒏𝒊𝒐𝒏 𝒓𝒖𝒍𝒆𝒔 ๑ !! 𝓛𝒊𝒔𝒕 𝒐𝒇 𝒓𝒐𝒍𝒆𝒔 ୭ .. ꒰ 🪷 ꒱ ๑ 𝓒𝒓𝒖𝒔𝒉 𝒍𝒊𝒔𝒕 ◠ 〢 . ❯❯ ꒰ 🍵 ꒱ ୭ 𝓑𝒍𝒂𝒄𝒌 𝒍𝒊𝒔𝒕 . 彡 . 🤩🌟🌟🌟 🤩🌟🌟🌟 🤩. 𝟏𝟓𝟎𝟓 ✨ 𝟓𝟎𝟓 ✨ 𝟒𝟒𝟒

7 Jun 2025, 08:11 UTC58 viewsread 12 August 2026
Photo

◂ ───◞ ✦ ⌞ NAVIGATION ⌝ ✦◝ ─── ▸ ➿ ➿➿➿➿➿➿➿➿➿➿ ➿ . ⧫ ⌗🍒⌝ 🤩ist of roles 🤩 🤩ules chat ──── ( !! ) ➤ 🤩atent ◝ ❽ 🤩 . ➿ ➿➿➿➿➿➿➿➿➿➿ ➿ ⌗🥝 🤩nformation ⌝ 🤩dmin staff ‖⊢ . 🥭 . ➤ 🤩oost ──── ⧫. ⌗🍓⌝ ⧫◞ 🤩ik tok ➿ ➿➿➿➿➿➿➿➿➿➿ ➿ ◂ ───◞ ✦ ⌞ INITIALS ⌝ ✦◝ ─── ▸

23 Mar 2025, 09:50 UTC175 viewsread 12 August 2026
Photo

˗ˏˋ 🤩 ⧼ 🤍𝐀𝐕𝓘𝐆𝐀𝐓𝐈𝓞𝐍 ⧽ ┊ 🪷 奪づ ! ´ˎ˗ ➿➿➿➿➿ ┈┈┈┈┈ ➿➿➿➿➿ ↼┈۫ 𑁍➿ ᘞᘡ 🤩𝐇𝓐𝐓 ᘡᘞ ➿𑁍 ┈۫ ⇀ ⌗𝓡𝐮ℓ𝐞𝐬 ❞ , 𝓘𝐧𝖎𝐭𝖎𝐚ℓ𝐬 ❞ , 🪷୧𓂃 ᚐ ˙. ౨˙. ৎৎ ‹ ⌗🪷 . 、 ‹ ⌗🗝 ⌗𝓛𝖎𝐬𝐭 ơ𝐟 𝐫ơℓ𝐞𝘀 ❞, ↼┈۫ 𑁍➿ ᘞᘡ 🤩𝐍𝓘𝓞𝐍 ᘡᘞ ➿𑁍┈۫ ⇀ ˙. ❝ 𝓡𝐮ℓ𝐞𝐬, ⌗🗝 . ❝ 𝓕𝐚𝐦𝖎ℓ𝐲 𝓤𝐧𝖎𝐨𝐧𝐬 ྀ𓂃ׄ ↼┈۫ 𑁍➿ ᘞᘡ 🤩𝐓𝐇𝐄𝓡 ᘡᘞ ➿𑁍┈۫ ⇀ ˙. 𝓐𝐧ơ𝐧 ❞ , 𝓟𝐚𝐭𝐞𝐧𝐭 ❞ ‹ ⌗🪷 . 、 ౨. ৎৎ ‹ ⌗🤩 . 、 ‹ ⌗🗝, 𝓘𝐧𝐟ơ ❞, 𝓐𝐝𝐦𝖎𝐧 ❞ ➿➿➿➿➿ ┈┈┈┈┈ ➿➿➿➿➿

23 Mar 2025, 09:47 UTC135 viewsread 12 August 2026
Photo

「 🥺🥳🤯😣🙁🥳🤬😣😢🥺 」 ➿➿➿➿➿➿➿➿➿➿➿ . ༄ ✨ ─ׂ┄ 𝓐𝒏𝒐𝒏 𝒎𝒆𝒔𝒔 𝇈彡 ˙ . ༄ 🤩 ─ׂ┄ 𝓟𝒂𝒕𝒆𝒏𝒕 ౿ ˙. . . ༄ 🩷 ─ׂ┄ 𝓑𝒐𝒐𝒔𝒕 … . 𝜗𝜚. ➿➿➿➿➿➿➿➿➿➿➿

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

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.

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

“❯❯ ᑕᕼɆᗷᑌ'S ꕤ ᑭØᖇTᖴØᒪIØ !!” (@chebusport), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/chebusport.

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.