Channel
@WEGFGHDFH
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,661subscribers
-24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001901115301 |
|---|---|
| Type | Channel |
| Username | @WEGFGHDFH |
| Created | Between 1 March 2023 and 31 December 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/WEGFGHDFH |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 04:33 | 1,661 | -4 |
| 20 Aug 2026, 10:37 | 1,665 | -5 |
| 17 Aug 2026, 14:26 | 1,670 | -6 |
| 14 Aug 2026, 01:48 | 1,676 | -5 |
| 11 Aug 2026, 05:18 | 1,681 | -5 |
| 7 Aug 2026, 19:36 | 1,686 | +1 |
| 7 Aug 2026, 16:47 | 1,685 | first reading |
5 posts held, back to 1 August 2026 — the 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.
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. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 5 (1 August 2026 – 6 August 2026) |
| Views total | 240 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:47 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.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👌 | 2 | 50.0% | |
| 👍 | 2 | 50.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 3 of the 5 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 1 August 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🇯🇵 東京獨旅｜吃東西真的太幸福了🍜🍮 不踩雷的點~ 1. 🥇 HAJIME 日本橋炸豬排 ★★★★★ 2. 🍜 鴨 to 蔥 淺草拉麵 ★★★★ 3. 🍳 Yellow 表參道蛋包飯 ★★★☆ 4. 🍓 Sweet Box 竹下通可麗餅 ★★★☆ 5. ☕️ 星巴克典藏® 東京晴空塔城 30F ★★★☆ 6. 🥄 PUDDING LAB Ginza 銀座布丁專賣店 ★★★★ 7. 🥞 紅鶴 淺草舒芙蕾 ★★★★ 8. 🍜 Ichikakuya Asakusa 壹角家橫濱家系拉麵 ★★★★☆ 9. 🐟 淺草街邊鯛魚燒 ★★★ 10. 🍔 東京迪士尼餐廳 ★★★ 11. 🍫 日本麥當勞（巧克力奶昔） ★★★★★ 12. 🥤 711 果昔 ★★★☆ 13. 🍓 Seven 砂糖樹（Sugar Butter Tree）草莓口味 ★★★★☆ 14. 💊 711 消除疲勞好物 ★★★
👍2
日期 8/1（六） 🎆 教祖祭 PL 花火藝術（日本最大級煙火之一） 富田林市 8/2（日） 天神祭遺留夏季活動、大川散步 天滿橋 8/3（一） 梅田藍天大廈空中庭園夜景 梅田 8/4（二） 道頓堀美食巡禮、固力果跑跑人夜景 心齋橋／難波 8/5（三） TeamLab Botanical Garden Osaka（夜間光影展） 長居植物園 8/6（四） 新世界、通天閣夜景 新世界 8/7（五） 大阪城公園夏日散步、夜間點燈 大阪城 8/8（六） SUMMER SONIC OSAKA（第一天） 舞洲 8/9（日） SUMMER SONIC OSAKA（第二天） 舞洲 8/10（一） 海遊館＋天保山摩天輪夜景 港區 8/11（二） 阿倍野 HARUKAS 展望台 天王寺 8/12（三） 美國村、潮流服飾、美食 心齋橋 8/13（四） 盂蘭盆節開始、各神社盆踊 大阪市各區 8/14（五） 住吉大社夏祭 住吉…
👌1
🎆 東京地區：8 月高福利花火大會與祭典 1. 麻布十番納涼祭（麻布十番納涼まつり） 福利亮點：完全免費入場！ 這是東京公認「美食CP值最高」的夏日祭典。全日本各地的名產老店都會在此設攤，提供限定折扣與平價美味，還有免費的街頭藝人表演與傳統文化節目。 時間：8月下旬（約 15:00 – 21:00） 2.高圓寺阿波舞（高円寺阿波おどり） 福利亮點：全台/全街道免費觀賞！ 超過萬名舞者在 8 大商店街免費巡遊，周邊商家會推出「夏祭限定折價啤酒與小吃」，現場氣氛極熱烈，不需要買任何門票就能沉浸式體驗。 時間：8月下旬 17:00 – 20:00 3.神宮外苑花火大會（第45回 神宮外苑花火大会） 時間：8月8日（週六）19:30 – 20:30 地點： 及秩父宮橄欖球場周邊 交通：JR「信濃町站」/「千駄谷站」或都營大江戶線「國立競技場站」步行 5 分鐘 亮點：東京都心少有的煙火盛事，採全預售票制。結合知名歌手與藝人的現場表演演…
👌1
花蜜閣推薦你的8月份出差或旅遊活動 8/1（六） 🎆 江戶川花火大會、🎆 板橋花火大會、銀座浴衣活動 江戶川／板橋／銀座 8/2（日） TOKYO IDOL FESTIVAL、迪士尼夏季活動 台場／舞濱 8/3（一） 歌舞伎納涼公演 六本木夜景 銀座／六本木 8/4（二） 東京鐵塔夏季點燈、麻布台 Hills 夜景港區 8/5（三） TeamLab、豐洲夜景 豐洲 8/6（四） 上野夏祭、市集、阿美橫町 上野 8/7（五） 八王子祭（第一天） 八王子 8/8（六） 🎆 神宮外苑花火大會、台場海濱煙火 明治神宮外苑／台場 8/9（日） 八王子祭（最熱鬧） 八王子 8/10（一） 晴空塔夏季活動 押上 8/11（二） Summer 展覽、動漫展 池袋／六本木 8/12（三） 新宿夜市、美食巡禮 新宿 8/13（四） 盂蘭盆節（Obon）開始、各地盆踊 東京各區 8/14（五） 明治神宮 Bon Odori 明治神…
📅 8月東京花火大會時間表 📍 8/1(週六) 江戶川區花火大會 前5分鐘瞬間發射1,000發！全日本頂級的超豪華超密集開場！ 📍 8/1(週六) 板橋花火大會 長達300米的「尼亞加拉大瀑布」煙花+超大尺玉，視覺效果絕了！ (※ 注意：今年免費觀賞區搬到了高島平站附近，別走錯啦) 📍 8/8(週六) 明治神宮外苑花火大會 在市中心一邊看演唱會一邊賞煙花！音樂與火光的雙重盛宴！(※ 100%預售門票制) 💡 觀賞實用小貼士 1️⃣ 提前確認門票！ 神宮外苑沒有免費看台，必須提前在官網買票；板橋花火的免費區位置有變，記得提前查好路線。 2️⃣ 帶足現金！ 現場的小吃攤（屋台）大多不支援刷卡或電子支付，多準備點100日圓和1000日圓的零錢。 3️⃣ 散場不要急！ 散場時地鐵站會擠爆，建議演出結束後在周邊歇個1小時左右再走更輕鬆~
Showing the 5 most recent of 5 posts we hold for @WEGFGHDFH. 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 — 166,303 of 1,601,189entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“東京大阪-風景美食推薦” (@WEGFGHDFH), 1,661 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/WEGFGHDFH.
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.