Telegram RegisterThe public register of Telegram
Telegram profile photo for KOMA_VPN

Channel

KOMA_VPN

@KOMA_VPN

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 7 August 2026

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

Register entry

Telegram ID-1002186816350
TypeChannel
Username@KOMA_VPN
DescriptionEkiraningni ulash
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/KOMA_VPN

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 5 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:176no change
7 Aug 2026, 16:236first reading

Engagement

19 posts held, back to 9 September 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 19 posts for this entry, the most recent from 23 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Videos
8
Links
24

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.

Video runtime
43s
Average length
43s

Measured directly from 1 video 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

23 Sept 2025, 00:34 UTC21 viewsread 12 August 2026
File

ONWAY CHIT📂 🔹ANDROID 🔻SUPER SMOOTHNESS 🔻64 BIT ONLY 🔻HEAD SH^T ONLY 🔻GRAPHICS ARE UPGRADED 🔻NO LAG/NO ERROR 🔻IF YOU WANT NO BAN YOU MUST BUY VIP OBB 🔻SAFE PLAY 🎬 O'rnatish └ https://t.me/onway_isbot/90 ➿➿➿➿➿➿ 💥Vip haqida malumot: https://t.me/ONWAY_VIP/23

Signed Terideng

21 Sept 2025, 14:56 UTC19 viewsread 12 August 2026
File

GL VIP CHEAT📂 ✅ Функции AIM 300👍 ZALYUT 100☄️ BEZ BAN✔️

Signed Terideng

21 Sept 2025, 14:56 UTC16 viewsread 12 August 2026
File

GL VIP CHEAT ✅ Функции 🔻🤩🤩🧥🏀🏀🤩🤩🤩🤩🤩🤩🤩 🔻 𝗡𝗢 𝗕𝗔𝗡 ➿➿➿➿➿➿

Signed Terideng

21 Sept 2025, 14:56 UTC22 viewsread 12 August 2026
File

GL MOD CHIT📂 ✅ Функции 🔻- 777фпс 🔻- фикс лагов 🔻- нет фризов 🔻- стабильный фпс 🔻 𝗡𝗢 𝗕𝗔𝗡 ➿➿➿➿➿➿

Signed Terideng

21 Sept 2025, 14:55 UTC13 viewsread 12 August 2026
File

🌟 Vpn 🌟 ⚠️ Есле не сложно оставьте отзыв в комментариях ⚠️

Signed Terideng

21 Sept 2025, 14:55 UTC11 viewsread 12 August 2026
File

💎 Регистрация урона, стабильнее пинг, мини залёт, плавнее игра, меньше задержки, для всех режимов, без бана. Silar uchun shuncha harakat qilyabman❤️

Signed Terideng

21 Sept 2025, 14:54 UTC12 viewsread 12 August 2026
File

🌐𝗩𝗣𝗡🌐𝗛𝘂𝘀𝘂𝘀𝗶𝘆𝗮𝘁𝗹𝗮𝗿𝗶 🩸🩸🩸 💎-𝗣𝗜𝗡𝗚- 20-30 𝘂𝘀𝗵𝗹𝗮𝗯 𝗯𝗲𝗿𝗮𝗱i 🔘 💎-𝗥𝗲𝗴𝗮 𝗽𝗶𝘇𝗱𝗲𝘀 𝗯𝗼𝗹𝗮𝗱𝗶 🔘 💎-N𝗲𝗿𝗲𝗮𝗹𝗻𝗶𝘆 𝗸𝗶𝗹𝗹𝗮𝗿 𝗯𝗼𝗹𝗮𝗱𝗶 🔘 💎-𝗩𝗮𝘀𝗵𝗲 𝘁𝗲𝘇 𝗸𝗶𝗹𝗹𝗮𝗿 ( 𝘃𝗽𝗻𝗻𝗶 𝗸𝘂𝗰𝗵𝗶🔘) ▶️ O'RNATISH VIDEO CLICK HERE ⚡ Telegram channel @GL MOD

Signed Terideng

21 Sept 2025, 14:54 UTC10 viewsread 12 August 2026
File

🌐CFG-💀➕0.0.0 ping🔘 ⚙️-120FPS O'YINDA SEZILADI✅ ⚙️-HEADSHOT 2/3✅ ⚙️-120FPS QOTISH YOQ✅ ⚙️-PING 20/30✅ 🛡PAROLL:05GLMODCFG1070900PING ▶️ O'RNATISH VIDEO CLICK HERE ⚡ Telegram channel @GL MOD

Signed Terideng

12 Sept 2025, 18:13 UTC16 viewsread 12 August 2026
File

💜💜💜💜💜0⃣💜💀💜4⃣ 🎮 4.0 GL / 64 / 32 😈 HEAD SHOT MAX 😈 HIGH DAMAGE 😈 ANY NO ERROR 😈 NO CRASH 😈 TDM / BOX FULL SUPPORT 😈 ALL MAP WORKING 😈 SAFE 🔐No Password ▶️ OʻRNATISH VIDEO ➡️ CLICK ✔️Feedback -@MRX_CHITER

Signed KAMOL

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

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

“KOMA_VPN” (@KOMA_VPN), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/KOMA_VPN.

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.