Telegram RegisterThe public register of Telegram

Channel

花吹雨

@HomeSweetHome520

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

102subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003963959215
TypeChannel
Username@HomeSweetHome520
Description匆匆过客,夜夜雨落。
CreatedBetween 1 April 2026 and 12 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/HomeSweetHome520

Growth

1028 Aug 2026, 13:00 — 102 subscribers9 Aug 2026, 10:02 — 102 subscribers8 Aug 2026, 13:009 Aug 2026, 10:02
2 measurements taken within a single day. 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 101–103 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 10:02102no change
8 Aug 2026, 13:00102first reading

Engagement

20 posts held, back to 12 June 2026the 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 · 30 days
1524.6%
avg views ÷ 102 subscribers
Avg views / post
1,560
9 posts measured
Reaction rate
0.048%
reactions ÷ views · ER floor
Posts in window
14
of 20 held

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 5 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (12 June 20264 August 2026)
Views total13,996
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 10:02 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.

What this channel posts

Photos
23
Videos
5
Links
2

Lifetime counters from Telegram’s own channel header, read 9 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
3m 21s
Average length
40s

Measured directly from 5 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

10 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10100.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 8 of the 20 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 20 most recent posts we hold, published 12 June 2026 to 4 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.

Recent posts

4 Aug 2026, 15:53 UTC106 views1 reactionsread 9 August 2026
Video

【花名】: #小鱼(@wm200371wm) 【天时】:26年8月上旬 【地理】: 蓉城红枫岭 【水费】: 7p11pp 【回忆】: 重庆妹妹,身高161,干瘪的A。 脸上有些岁月的痕迹了,但人照还算一致,之前抖音跳舞,现在行情差了下水。除了熊其他其实分数可以打高一些,但是干瘪的胸观感太差了,一整场铺垫好的情绪,在我看到她脱下胸罩露出那干瘪的乳房,我的所有兴奋跟她胸一样像是被什么东西榨干了一样,唉,写不下去了,不推荐。 【量化】:颜值22+身材12+软件20+声音6+偏爱4=64 【标签】:#抖音主播 不推荐

1

1 Aug 2026, 13:53 UTC181 views1 reactionsread 9 August 2026
Photo

【花名】: #幼辞 (@youci888) 【天时】:26年8月上旬 【地理】: 蓉城驷马桥 【水费】: 11pp(报告减一) 【回锅】: 精子、时间都很宝贵,挑自己喜欢的体会,这是我写回锅报告的前提。鉴于这次约辞宝的体验又上了一层新的台阶,所以我愿意让她来担任首篇回锅报告的女主。 在我有限的出击生涯中,目前辞宝的口活最为夸张,这次进化成从三角区开始亲吻,然后随着鼻息转移到蛋蛋,再由下而上,软糯的小舌快速扫过根部,像吃一根即将化掉的老冰棍,她不允许有丝毫液体滴落,裹着液体径直含住头部,然后迅速吞吐起来。一旦摸索到你的敏感点,灵活的舌头像搅拌器一样旋风攻击,口液夹杂喉液咕嘟作响,那忘我的表情分明就是她传递出的情绪,绷紧的脚趾和扭曲的身体就是我的回应。之前也会趁着肉棒湿润难耐用她的一对浑圆将你包裹,定力不好一定要提前沟通免得被秒。 女骑士名声在外,辞宝的女上花样多,幅度大。鸭子蹲,整根没入的同时中途时不时变向,我感觉整个人被抛

1

31 Jul 2026, 15:10 UTC701 viewsread 9 August 2026
Video

【花名】: #晨曦(@chenxi9999988) 【天时】:26年7月下旬 【地理】: 蓉城牛市口 【水费】: 7p13pp 【回忆】: 自贡妹妹,身高163,B-,虽然开始看到颜值不是我喜欢的类型,耐不住好兄弟一直安利,又只有4分钟路程,果断出手看看成色,人照与视频一致。 浑身陶瓷白,凑近抱住一闻,香水与发香阵阵透来,浴室里的灯光下我俩像黑白双煞。大眼瞪小眼,大嘴吃小嘴,妹妹小双眼皮,脸蛋属于耐看。润达丰新的loft现在改得好漂亮,特别温馨,床边一个落日灯氛围直接拉满。 妹妹兼职下水不久,口技和女上都笨笨的,小小蹦跶两下只有我来接招。传教士轻点两下,随着卖力的舌吻很快就涌出水来,妹妹最近工兵接得有点多,下体有点小痛,也不想她太难受,抽出手打一会仍未出水,开始今天的重头戏。 这是不输雨宝的果冻舌头,小巧软糯,搅拌在一起又充满力量在我口腔横冲直撞。传教士边舌边夺,很快就能打开她的开关,吻到深处突然两边一起抽出,急得她伸出

30 Jul 2026, 16:55 UTC199 viewsread 9 August 2026
Forwarded from @danbaoyangyu_clipVideo

#舔逼 技术这一块(看视频真的会进步吗)

30 Jul 2026, 10:37 UTC208 viewsread 9 August 2026
Photo

【花名】: #小乖(@XGang06) 【天时】:26年7月下旬 【地理】: 蓉城成都东站 【水费】: 6p11pp 【回忆】: 重庆妹妹,身高160,D-。人如其名,本人线下也是小乖小乖的。 人照8,穿着显瘦,脱衣有肉的代表,肉肉很懂事的胖在了该胖的地方。很爱卫生的妹妹,口一会,用纸巾擦了接着口。特点是舌头快速抖动来刺激冠状沟,然后把蛋蛋包在嘴里吞吐。 嫩妹永远值得相信的肉体,细腻滑嫩,夸她还会不好意思别过头去。熊大而挺,触感极佳,让匈奴人吃爽了。 爱爱体验中规中矩,但下面极其水润,让我在女上、传教,短暂的后入后为了加强刺激只能换成趴入,软趴趴的屁股坐上去太爽了,迅速出水。 可惜没有舌,事前事后的调情呵护也少点意思,不然应该是妥妥的小红牌。不过妹妹开课也很佛系,坦言道开多了身体也吃不消,那就随缘吧。 【量化】:颜值23+身材21+软件17+声音7+偏爱6=74 【标签】:#童颜巨乳 可打卡

24 Jul 2026, 11:33 UTC401 views1 reactionsread 9 August 2026
Video

【花名】: #小鱼仔(@fairytail5216) 【天时】:26年7月下旬 【地理】: 蓉城公元汇 【水费】: 7p11pp 【回忆】: 湖北妹妹,身高163,B+。一波三折,还好妹妹休红较快,让我在离蓉前约上了。 略卡粉,妆后人照基本一致,黄皮,好在皮肤细腻,略有医美,不过不是公式化美女,腰细腿长,于我而言算是超值。 进门闲聊两句,直接躺在沙发上把腿支到我怀里任我把玩,话唠小妖精,腰一搂就抱上来亲亲。按在床上亲胸只舔得她娇喘连连,声音太美妙了,只想立马把她的音响拧到最大。 妹妹敏感的像是一块已经吸饱水的海绵,任何轻微的外力稍加挤压,她就不住的迸出水来。她甚至只是刚坐上来,还没来得及动,下体就是一阵收缩袭来,声音变得急促,整个人软趴趴瘫我怀里。 传教士,九浅一深,每一次深入,就像长号把滑管拉回,随之而来就是高亢的女高音,如此四五个来回,妹妹已如筛糠般抖动起来,那种不自觉的抽颤简直把人的魂都勾走了。“哥哥,我,不行…

1

22 Jul 2026, 13:50 UTC≈2,370 viewsread 9 August 2026
Photo

【花名】: #橘喵(@Sq19i) 【天时】:26年7月下旬 【地理】: 蓉城皇庭假日 【水费】: 7p12pp 【回忆】: 哈尔滨妹妹,身高160,C。饭饱思淫欲,突然想约一下在各个狼友群里时不时摇一摇的橘喵。 人照基本一致,肉肉集中在肚子和大腿上,脱衣前并不明显,手臂纹了些许星星,背后纹了六尾狐,勉强能吃。不愧是东北妹妹,破冰挺自然的,口音是东北饺子馆常听的那种,搭上一张大眼萌妹的脸略有反差。 口活中规中矩,69小蝴蝶倒是让我吃得很爽,看得出来妹妹比较敏感,被口得倒吸气。女上摇一摇,我脑子里总感觉有BGM在响。转传教士突然软掉,妹妹让我冲一下重新口,态度没的说。水是真多,二次插入直接啪啪作响,小趴菜又是一次快速出货。 目前开7略软,不过好在底子不错,相信减肥成功以后能得到更多人的喜欢。 【量化】:颜值23+身材20+软件18+声音7+偏爱6=74 【标签】:#反差甜妹 可打卡

20 Jul 2026, 21:21 UTC≈2,760 views1 reactionsread 9 August 2026
Photo

【花名】: #小蛋挞(@wacxdt) 【天时】:26年7月中旬 【地理】: 蓉城摩玛新城 【水费】: 6p10pp 【回忆】: 广西妹妹,用广西话说表锅一起来七螺狮昏真的超级搞笑,身高162,18岁,A+,黄皮,但皮肤细腻光滑,是自认为甜御参半的御姐。 这个代哥是真会做人,这种天气居然想出来高温补贴这一手,妹妹人照一致,略有卡粉并不影响原生丽质。我一般不会对瘦妹的身材打高分,但是小蛋挞瘦的很健康,线条十分流畅,是一种健康蓬勃朝气的美。 口活不错,是舌头在蘑菇头上打转,然后啵地吸一口,瞬间就让二弟气鼓鼓。应该是今天吃潮汕牛肉料碟打了蒜,其他报告常见的大蟒蛇到我这只是轻轻一吻并不过瘾。并且因为做了美甲的原因让我自己戴套弄软了好几个来回。 有特色的是女上,虽然她动作并不娴熟,但是时不时会夹你一下,有点小舒服。今天也是第一次体验了丝足,原来是需要美腿来充当开启一个新性癖的钥匙。趴入屁股是真的软,让本就对该姿势敏感的我,耸动几下

1

Showing the 12 most recent of 20 posts we hold for @HomeSweetHome520. 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 — 539,501 of 1,350,102entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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

“花吹雨” (@HomeSweetHome520), 102 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/HomeSweetHome520.

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.