Telegram RegisterThe public register of Telegram
Telegram profile photo for 法拉利🏎VIP異國車庫

Channel

法拉利🏎VIP異國車庫

@ezzzz399

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

2,080subscribers

-46 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002120942555
TypeChannel
Username@ezzzz399
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/ezzzz399

Growth

2,0802,1262,1037 August 2026 — 2,126 subscribers7 August 2026 — 2,126 subscribers8 August 2026 — 2,125 subscribers11 August 2026 — 2,122 subscribers14 August 2026 — 2,115 subscribers18 August 2026 — 2,107 subscribers21 August 2026 — 2,097 subscribers24 August 2026 — 2,087 subscribers27 August 2026 — 2,083 subscribers30 August 2026 — 2,080 subscribers7 August 202630 August 2026
10 measurements spanning 22 days, net -46. 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 2,073–2,133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 05:262,080-3
27 Aug 2026, 15:072,083-4
24 Aug 2026, 20:132,087-10
21 Aug 2026, 00:332,097-10
18 Aug 2026, 00:422,107-8
14 Aug 2026, 14:282,115-7
11 Aug 2026, 15:362,122-3
8 Aug 2026, 14:222,125-1
7 Aug 2026, 20:312,126no change
7 Aug 2026, 18:322,126first reading

Engagement

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

What this channel posts

Video runtime
1m 28s
Average length
15s

Measured directly from 6 videos 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

23 reactions across 10 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
23100.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 10 of the 14 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 23reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 27 December 2025 to 28 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

28 Dec 2025, 15:47 UTC≈4,470 views9 reactionsread 7 August 2026
Photo

小瑜瑜🇻🇳 💕 青春,可愛,顏值高,中文溝通 155/42/19y/D 舌吻/無套吹/69/水中簫/品鮑/按摩/殘廢澡/無套+1000(內射)/口爆+500/3+1(200分鐘) 💰 3100/30/1 3500/50/1 4000/60/2 4900/90/2(提前告知) #中和區

9

28 Dec 2025, 15:44 UTC≈3,670 views3 reactionsread 7 August 2026
Photo

學生妹🇹🇼首度下海 163/46/22y/C 上班時間:下午2點到半夜12點(12點最後一個開始) 舌吻/無套吹/殘廢澡/按摩/69 💰 3900/30/1 4300/50/1 4800/60/2 #中和區

3

28 Dec 2025, 09:14 UTC≈2,970 views1 reactionsread 7 August 2026
Photo

沙拉💎162 50 E ⏰13:00~03:00 ❤️服務項目❤️ 殘廢澡 舔蛋 品鮑 69 奶炮 胸推 屁推 無套吹 按摩 舌吻 水中蕭 💚加值服務💚 ⭕️入珠 ⭕️口爆+500 ⭕️顏射+500 ⭕️後門+1000 ⭕️兩男一女 ⭕️買3送1。買5送3。 💰 3300/30/1S 3500/50/1S 4000/60/2S 4700/90/2S #板橋區

1

28 Dec 2025, 09:14 UTC≈2,570 views3 reactionsread 7 August 2026
Photo

心跳💎158 48 C ⏰13:00~03:00 ❤️服務項目❤️ 殘廢澡 舔蛋 品鮑 69 奶炮 胸推 屁推 無套吹 按摩 水中蕭 舌吻 💚加值服務💚 ⭕️毒龍 ⭕️口爆+500 ⭕️無套內射+1000 ⭕️兩男一女 ⭕️買2送1。買3送1。買5送3。 💰 3300/30/1S 3500/50/1S 4000/60/2S 4700/90/2S #板橋區

3

28 Dec 2025, 09:10 UTC≈2,080 views1 reactionsread 7 August 2026
Photo

米米163 E 48kg 💲30分鐘1S 3200 💲50分鐘1S 3400 💲60分鐘2S 3900 💲90分鐘2S 4400 👉本人照,20y 真奶 服務(:) 🔸舌吻🔸殘澡🔸奶炮 🔸無套吹🔸共浴🔸舔蛋 🔸按摩 🔸69 🔸品鮑 🔸毒龍+100 🔸深喉 🔸自慰秀+200 🔸艷舞+300 🔸口爆+500 🔸顏射+500 🔸吞精+500 🔸無套內射+1000 🔸攝影不露臉+1000 🔸攝影露臉+2000 🉑入珠+500 🔸絲襪誘惑(客人自備) 🈚️妊娠紋🈚️抽菸🈚️牙套 #板橋區

1

28 Dec 2025, 09:09 UTC≈1,750 views1 reactionsread 7 August 2026
Photo

柔菲161 F 48kg 💲30分鐘1S 3200 💲50分鐘1S 3400 💲60分鐘2S 3900 💲90分鐘2S 4400 👉本人照,22y真奶 膚白 服務(:) 🔸親親🔸殘澡🔸奶炮 🔸品鮑 🔸69🔸無套吹 🔸共浴🔸按摩🔸足交 🔸自慰秀+200 🔸口爆+500 🔸無套內射+1000 🔸攝影不露臉+1000 🉑入珠+500 🔸絲襪誘惑(客人自備) 🈚️妊娠紋🈚️抽菸🈚️刺青🈚️牙套 #板橋區

1

28 Dec 2025, 09:08 UTC≈1,510 views1 reactionsread 7 August 2026
Photo

♣️語芯♣️毒龍鑽我最強🔥超強服務派 🔥特色:🔸真奶🔸膚白🔸無妊娠紋🔸剃毛🔸無牙套 👗密碼:160/真H/26y/52kg ⏳時間:13:00-02:00 👍項目:無套吹/共浴/親嘴/舌吻/品鮑/69/舔蛋/奶炮/水中蕭/胸推/屁推/按摩/毒龍 *可配合: 高跟鞋 性感睡衣 絲襪 情趣用品(客自備) ✅口爆+500✅顏射+500✅露珠+500✅攝影不露臉+1000 🉑2+1(150/2)🉑3+1(200/3)🉑5+3(400/5-包夜) 💰: 1s/30min/3300 1s/50min/3600 2s/60min/4100 2s/90min/4800 #板橋區

1

27 Dec 2025, 15:29 UTC≈1,440 viewsread 7 August 2026
Photo

🌟豆花妹 🇻🇳 👠160/36E/45kg A餐 1s/30分/3700 B餐 1s/50分/4200 C餐 2s/60分/4700 無套吹>小親親>舌吻LG(視口腔衛生而定)>品鮑69>舔蛋舔睪丸>🐲毒龍鑽🐲>親胸>奶炮>包夜5+3>簡易按摩>情趣用品>絲襪誘惑(客自備) 豆花妹 🇻🇳 加值服務: 1. 戴口罩攝影:+1000 🔥青春辣妹 火辣身材 親切體貼的服務 #中山區

27 Dec 2025, 15:28 UTC≈1,270 views2 reactionsread 7 August 2026
Photo

琪蘿 🇻🇳 👠162/34D/48kg A餐 1s/30分/3700 B餐 1s/50分/4200 C餐 2s/60分/4700 無套吹>小親親>舌吻LG(視口腔衛生而定)>品鮑69>舔蛋舔澤丸>足交>奶炮>簡易按摩>情趣用品>絲襪誘惑(客自備) #中山區

2

27 Dec 2025, 15:27 UTC≈1,160 viewsread 7 August 2026
Photo

🌟嘉欣 🇻🇳 👠168/36F/50kg A餐 1s/30分/3700 B餐 1s/50分/4200 C餐 2s/60分/4700 無套吹>小親親>舌吻LG(視口腔衛生而定)>品鮑69>舔蛋舔睪丸>親胸>奶炮>足交>簡易按摩>情趣用品>包夜5+3>絲襪誘惑(客自備) 嘉欣 🇻🇳 加值服務: 1. 口爆:+500 2. 顏射:+1000 3. 自衛秀:+500 🔥高挑亮麗 溫柔體貼 值的愛愛和推薦 #中山區

27 Dec 2025, 15:23 UTC≈1,020 viewsread 7 August 2026
Photo

奶昔❤️ 22歲 上班時間:🌕12:00~🌙01:00 ❤️152/44/真C奶❤️ 流利中文 基本服務: 🉑共浴🉑無套吹🉑舌吻 🉑舔蛋🉑品鮑🉑69 🉑奶炮🉑胸磨臉🉑冰火 🉑按摩🉑胸推🉑屁推 🉑自慰秀🉑情趣用品(客自備) 🉑絲襪誘惑 💰 3300/40/1 3800/60/1 4300/60/2 4800/90/2 💵加值服務 💖射顏+500 🔥多節優惠 ➡️2+1(180分鐘2S) #中山區

27 Dec 2025, 15:21 UTC895 views1 reactionsread 7 August 2026
Photo

太陽❤️ 22歲 上班時間:🌕12:00~🌙01:00 ❤️155/42/真B奶❤️ 基本服務: 🉑共浴🉑無套吹🉑舌吻 🉑舔蛋🉑品鮑🉑69 🉑奶炮🉑胸磨臉🉑冰火 🉑按摩🉑胸推🉑屁推 🉑自慰秀🉑情趣用品(客自備) 🉑絲襪誘惑 💰 3400/40/1 3900/60/1 4400/60/2 4900/90/1 💵加值服務 💖口爆+500 💖射顏+500 🔥多節優惠 ➡️2+1(180分鐘2S) ➡️3+1(240分鐘3S) #中山區

1

Showing the 12 most recent of 14 posts we hold for @ezzzz399. 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 — 425,520 of 1,628,524entries 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 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.

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

“法拉利🏎VIP異國車庫” (@ezzzz399), 2,080 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ezzzz399.

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.