Telegram RegisterThe public register of Telegram
Telegram profile photo for 東京總瀏(訂閱不迷路)

Channel

東京總瀏(訂閱不迷路)

@sk6826

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

129subscribers

+1 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-1002448500163
TypeChannel
Username@sk6826
Created14 November 2024measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/sk6826

Growth

128129128.57 August 2026 — 128 subscribers9 August 2026 — 128 subscribers16 August 2026 — 129 subscribers7 August 202616 August 2026
3 measurements spanning 8 days, net +1. 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 128–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 06:29129+1
9 Aug 2026, 02:00128no change
7 Aug 2026, 23:32128first reading

Engagement

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

What this channel posts

Video runtime
22s
Average length
22s

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.

Reaction mix

10 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
550.0%
👍220.0%
🥰220.0%
🔥110.0%

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 5 of the 8 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 14 November 2024 to 23 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

23 Dec 2025, 16:36 UTCviews —

東京總瀏(訂閱不迷路) pinned «🍇私密美優客服 @jp5288 或點擊鏈接:https://t.me/jp5288 🍉東京外約新手上路 @mv5206 或點擊鏈接:https://t.me/mv5206 🍒優質日本女孩 @JP14182 或點擊鏈接:https://t.me/JP14182 🍅日本外送客評 @bj52068 或點擊鏈接:https://t.me/bj52068 🔞日本AV成人世界 @jpfc201 或點擊鏈接:https://t.me/jpfc201 👘東京愛情旅館 @jpmt141 或點擊鏈接:https://t.me/jpmt141»

10 Sept 2025, 18:51 UTC≈1,240 views1 reactionsread 9 August 2026
Photo

美優 東京 / 大阪 服務流程 & 說明 💋 服務特色 嚴選【日本素人・本人照保證】絕無照騙 完全預約制,全年無休 服務時間:每日 13:00 – 凌晨 24:00 接待不限國籍(日本、中國、台灣、香港、海外旅客皆可) ✅ 預約流程(新手必看) 1️⃣ 選擇女孩 先瀏覽頻道或網站照片,挑選喜歡的女生 (秋穗只提供本人照,絕對安心) 2️⃣ 確認資訊 告訴秋穗: 女孩編號 預約時間 約會地點(自宅 / 飯店) 👉 飯店需提供「房號」;若電梯需要房卡,需要客人下樓接送 3️⃣ 付款方式 現金(日圓)現場支付給女生 總金額 = 女孩服務費 + 交通費 4️⃣ 注意事項 請盡量提前預約,方便安排 女生會準時抵達,服務細心、自然,像戀人般親密 💸 服務費用 普通女孩:30,000 日圓起 中等女孩:50,000 日圓起 高檔女孩:80,000 日圓起 🚗 交通費(車馬費) #東京內:【車資 3000】 新宿區、豐島區、中央區、

1

14 Nov 2024, 09:11 UTC≈1,430 views3 reactionsread 9 August 2026

🍒🍒請保存此賬號 @sk6826 所有群組的最新動態都將在此頻道發布 以免群組遺失請務必加入 https://t.me/sk6826

1👍1🥰1

14 Nov 2024, 09:03 UTC≈1,440 views1 reactionsread 9 August 2026

🍇私密美優客服 @jp5288 或點擊鏈接:https://t.me/jp5288 🍉東京外約新手上路 @mv5206 或點擊鏈接:https://t.me/mv5206 🍒優質日本女孩 @JP14182 或點擊鏈接:https://t.me/JP14182 🍅日本外送客評 @bj52068 或點擊鏈接:https://t.me/bj52068 🔞日本AV成人世界 @jpfc201 或點擊鏈接:https://t.me/jpfc201 👘東京愛情旅館 @jpmt141 或點擊鏈接:https://t.me/jpmt141

👍1

14 Nov 2024, 08:49 UTC≈1,320 views5 reactionsread 9 August 2026

#點擊 鏈接 切換想要的語言 🇹🇼繁体中文 https://t.me/setlanguage/zh-hant-beta 适用于:所有系统平台 🇨🇳简体中文 (langCN) https://t.me/setlanguage/zhlangcn 🇭🇰香港人口語 https://t.me/setlanguage/hongkonger 适用于:Android/iOS 简介:模仿香港人讲嘢時中英夹杂 🇯🇵日本语 https://t.me/setlanguage/ja-beta

3🔥1🥰1

Showing the 8 most recent of 8 posts we hold for @sk6826. 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.

Citation-graph rank

Citation-graph rank — 91,895 of 1,584,733entries 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.

Mentions

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

“東京總瀏(訂閱不迷路)” (@sk6826), 129 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/sk6826.

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.