Channel
@jyud147
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,189subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003433128764 |
|---|---|
| Type | Channel |
| Username | @jyud147 |
| Created | Between 1 November 2025 and 31 March 2026— 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/jyud147 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 05:03 | 1,189 | +6 |
| 20 Aug 2026, 10:06 | 1,183 | +2 |
| 17 Aug 2026, 16:26 | 1,181 | +2 |
| 14 Aug 2026, 01:44 | 1,179 | +4 |
| 11 Aug 2026, 02:41 | 1,175 | +2 |
| 7 Aug 2026, 23:32 | 1,173 | no change |
| 7 Aug 2026, 16:46 | 1,173 | first reading |
15 posts held, back to 13 May 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (13 May 2026 – 7 August 2026) |
| Views total | 13 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:32 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 of the 15 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 13 May 2026 to 7 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.
花蜜閣8月整月盂蘭盆限定額外福利 1.朋友帶朋友 你享受7折卷*額外2萬折扣卷 你朋友享受8折卷 2.生日壽星享買幾送幾+特殊服務*1 3.約雙飛買一送一或者是 送一個女生一小時馬上來服務 4.包夜8小時以上享特殊福利永久卷（東京大阪可使用） 5.進入花蜜閣店約妹都可指定試車女生，並且給出試車價。 6.盂蘭盆祭典抽獎禮： 凡滿額 10 萬日圓以上，即可參加「夏日祭典搖骰子尊榮抽獎」 7.交通/住宿尊榮補貼： 遠道而來 / 異地預約（東京、大阪） 憑當日車票或飯店憑證，現折 1～2 萬日圓交通住宿補貼~ 8.這個福利在提一下：提前預約減免2000日圓 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
花蜜閣瘋狂の8月份福利上新 A:提前預約減免2000日圓 單節折扣： 1.櫻花級3-5萬日圓 約一小時享減8折卷—9折卷 2.楓月級別6-9萬日圓 約一小時享受減少16000-30000 3.金鳳級別10-15萬日圓 約一小時享受7折+免交通費 4.翡翠級16-30萬日圓 約一小時享受6折 5.至高級31萬日圓-50萬日圓以上 享減少10萬日圓+神秘價值4萬驚喜包*免交通 統一約後享受： 1.免費特殊服務*1 2.免房費2萬日圓 多節折扣： 1.櫻花級5萬 買四送一小時 買八送兩小時 買12送三小時 買16送四小時 2.楓月級6萬-9萬日圓 6萬買三送一 7萬買三送一 8萬買二送一 9萬買二送二 3.金鳳級10萬-15萬日圓 +2萬日圓享受兩小時射兩次+情趣*1 +4萬日圓享受三小時射三次 +8萬日圓享受四小時射四次 +12萬日圓享受五小時射五次 4.翡翠級16萬-30萬日圓 +1萬日圓可享2小時射2次方案…
#東京紅牌櫻花級反饋 女生資訊：A：🔴4133
東京（紅牌）優選女生： A：🔵4125 B：🔵4142 C：🔵4156 D：🔵4175 E：🔵4213 F：🔵4219 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
東京（紅牌）優選女生： A：🟢4124 B：🟢4136 C：🟢4141 D：🟢4168 E：🟢4174 F：🟢4202 G：🟢4212 H：🟢4217 I：🟢4232 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
東京（紅牌）優選女生： A：🟡4123 B：🟡4130 C：🟡4131 D：🟡4144 E：🟡4153 F：🟡4173 G：🟡4184 H：🟡4224 I：🟡4227 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
東京（紅牌）優選女生： A：🟠4111 B：🟠4115 C：🟠4121 D：🟠4122 E：🟠4134 F：🟠4163 G：🟠4177 H：🟠4209 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
東京（紅牌）優選女生： A：🔴4133 B：🔴4147 C：🔴4162 D：🔴4190 E：🔴4213 F：🔴4228 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：tp1154 📱：@txiaonyz （相遇即是緣，靠譜的性福在眼前）
❤1
Channel name was changed to «花蜜閣東京🎌紅牌預約優選名單»
Channel photo updated
（東京6月份紅牌🥇優選出勤中） 紅牌一： 🔴番号：3949 紅牌二： 🔴番號：4050 紅牌三： 🔴番號：4067 紅牌四： 🟠番号：3950 紅牌五： 🟠番号：3956 紅牌六： 🟠番号：4051 紅牌七： 🟠番號：4027 紅牌八： 🟡番号：3951 紅牌九： 🟡番號：4005 紅牌10：（雙飛） 🟢番號：3996 🟢番號：3997 紅牌11： 🟢番號：4006 紅牌12： 🟢番號：4053 紅牌13： 🔵番号：3961 紅牌14： 🔵番号：3973 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：ffyk8 📱：@txiaonyz （相遇即是緣，性福在眼前）
（東京紅牌🥇優選出勤中） 價位：🟠楓月級 番號：4051 類型：新宿女僕咖啡店店長 ❄️162cm/Ecup/46kg/23y❄️ 特點介紹： 服務細心又貼心，互動自然不尷尬，親和力十足。特別照顧第一次體驗的新手，會主動引導氣氛，讓人能夠輕鬆放鬆下來。外表乖巧甜美，私下卻充滿反差魅力，活潑愛笑又很會手機翻譯聊天，整體相處感受舒適又愉快，讓人忍不住想再次見面～💕 ps：提前預約很重要喲 關於她的客評反饋： 👇👇👇👇👇 客评① 客评② 客評③ 🥰聯絡奈野子： ⭐：jpjtxn 📱：@j1542p 📱：jp1154 📱：@txiaonyz （相遇即是緣，性福在眼前）
Showing the 12 most recent of 15 posts we hold for @jyud147. 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 — 907,223 of 1,585,759entries 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.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@jyud147 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“花蜜閣東京🎌紅牌預約優選名單” (@jyud147), 1,189 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/jyud147.
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.