Telegram RegisterThe public register of Telegram
Telegram profile photo for 落雨夜猫AV频道

Channel

落雨夜猫AV频道

@nightcat_main_3

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

56subscribers

+54 since we began measuring on 7 November 2026

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

Register entry

Telegram ID-1004354678135
TypeChannel
Username@nightcat_main_3
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 November 2026
Last confirmed live8 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/nightcat_main_3

Growth

256297 Nov 2026, 16:22 — 2 subscribers8 Nov 2026, 01:07 — 56 subscribers7 Nov 2026, 16:228 Nov 2026, 01:07
2 measurements taken within a single day, net +54. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 01:0756+54
7 Nov 2026, 16:222first reading

Engagement

10 posts held, back to 7 November 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.8%
avg views ÷ 56 subscribers
Avg views / post
6.6
10 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
10
of 10 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held10 (7 November 2026 – 7 November 2026)
Views total66
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 16:22 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

Video runtime
9h 39m
Average length
57m 54s

Measured directly from 10 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 10 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 16:11 UTC2 viewsread 7 November 2026
Video

番号:SSHN-014 女优:永野いち夏 标题:超重磅毫无保留的大乱交8小时!!SODstar女优11名×无数肉棒108根=大量射精160发BEST!!! 原题:超ド級ハンパない大乱交8時間!!SODstar女優11名×無数のチ○ポ108本=大量射精160発BEST!!! 发行:2020-08-27 大小:20.24GB(2 个文件,第1个) 备注:同番号 2 个文件(分卷/多版本);SOD BEST 合集(共演)

7 Nov 2026, 15:28 UTC5 viewsread 7 November 2026
Video

番号:SSHN-008 女优:永野いち夏 标题:跨越厂牌界限的历代专属女优21人 舔到舌头融化的黏糊唾液搅拌、亲吻续杯无限的舌吻性交SP! 原题:レーベルの垣根を超えた歴代専属女優21人 レロレロ舌が溶けちゃうベチョベチョ唾液引っ掻き回しチュッチュおかわり無限ベロチュー性交SP! 发行:2020-07-23 大小:20.21GB(2 个文件,第2个) 备注:同番号 2 个文件(分卷/多版本);SOD BEST 合集(共演)

7 Nov 2026, 14:49 UTC4 viewsread 7 November 2026
Video

番号:SSHN-008 女优:永野いち夏 标题:跨越厂牌界限的历代专属女优21人 舔到舌头融化的黏糊唾液搅拌、亲吻续杯无限的舌吻性交SP! 原题:レーベルの垣根を超えた歴代専属女優21人 レロレロ舌が溶けちゃうベチョベチョ唾液引っ掻き回しチュッチュおかわり無限ベロチュー性交SP! 发行:2020-07-23 大小:20.21GB(2 个文件,第1个) 备注:同番号 2 个文件(分卷/多版本);SOD BEST 合集(共演)

7 Nov 2026, 14:15 UTC5 viewsread 7 November 2026
Video

番号:SSHN-001 女优:永野いち夏 标题:猛插猛插猛插不停!美女们疯狂高潮的激烈抽插 2枚组8小时20SEX 原题:突いて突いて突きまくる!美女たちのイキまくり激ピストン 2枚組8時間20SEX 发行:2020-05-21 大小:20.43GB(2 个文件,第2个) 备注:同番号 2 个文件(分卷/多版本);SOD BEST 合集(共演)

7 Nov 2026, 13:49 UTC5 viewsread 7 November 2026
Video

番号:SSHN-001 女优:永野いち夏 标题:猛插猛插猛插不停!美女们疯狂高潮的激烈抽插 2枚组8小时20SEX 原题:突いて突いて突きまくる!美女たちのイキまくり激ピストン 2枚組8時間20SEX 发行:2020-05-21 大小:20.43GB(2 个文件,第1个) 备注:同番号 2 个文件(分卷/多版本);SOD BEST 合集(共演)

7 Nov 2026, 11:58 UTC9 viewsread 7 November 2026
Video

91CM-182 手机的秘密 男友的情趣视频没想到却成我沦为性奴的把柄

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

Mentions

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.

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

“落雨夜猫AV频道” (@nightcat_main_3), 56 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/nightcat_main_3.

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.