Telegram RegisterThe public register of Telegram
Telegram profile photo for 日本接码语音 记事本

Channel

日本接码语音 记事本

@ribenappsms

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,109subscribers

+494 since we began measuring on 31 October 2026

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

Register entry

Telegram ID-1002304760632
TypeChannel
Username@ribenappsms
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 October 2026
Last confirmed live16 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/ribenappsms

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 16 November 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

6131,10986131 October 2026 — 615 subscribers1 November 2026 — 614 subscribers7 November 2026 — 613 subscribers16 November 2026 — 1,109 subscribers31 October 202616 November 2026
4 measurements spanning 16 days, net +494. 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 539–1,183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 21:471,109+496
7 Nov 2026, 12:57613-1
1 Nov 2026, 12:16614-1
31 Oct 2026, 16:22615first reading

Engagement

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

ERR · 30 days
16.2%
avg views ÷ 1,109 subscribers
Avg views / post
180
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 October 2026
Posts held20 (13 August 2026 – 29 October 2026)
Views total359
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Oct 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.

Reaction mix

7 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7100.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 6 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 7 reactions 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 13 August 2026 to 29 October 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

Telegram’s own ‘edited’ marker: 0 of 4 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).

28 Oct 2026, 17:11 UTC176 viewsread 31 October 2026
Photo

号码在这里 认准 +888 0427 5619

Signed 纽约接码@ribenapp

28 Oct 2026, 16:42 UTC183 viewsread 31 October 2026
Photo

又有客户被骗u了 打款之前确定下账号是不是+888 0427 5619号码

Signed 纽约接码@ribenapp

21 Oct 2026, 03:53 UTC355 viewsread 31 October 2026

出2个过line资料 需要的老板联系(ym+1,sb+1) @newyorkjiema

Signed 纽约接码@ribenapp

15 Oct 2026, 08:22 UTC492 viewsread 31 October 2026
Photo

电话+888 @ribenapp @linepifa @linegongchang 这是纽约接码的真实账号 +888号码和3个官方用户名

Signed 纽约接码@ribenapp

15 Oct 2026, 08:19 UTC383 views3 reactionsread 31 October 2026
Photo

这是骗子,大家小心!!!

❤3

Signed 纽约接码@ribenapp

12 Oct 2026, 12:17 UTC387 viewsread 31 October 2026

永旺价格调整:接到通知,永旺(AEON)价格调整为18.请及时给子账号调整价格,以免造成损失!谢谢!

Signed 纽约接码@ribenapp

9 Oct 2026, 16:37 UTC484 viewsread 31 October 2026

谁有打爆卡或者esim带流量的 联系 @newyorkjiema

Signed 纽约接码@ribenapp

6 Oct 2026, 01:08 UTC619 views0 reactionsread 31 October 2026

找: 日本粉商安装远控app 按照安装的台数给钱 能打的联系@newyorkjiema

Signed 纽约接码@ribenapp

16 Sept 2026, 14:33 UTC891 views1 reactionsread 31 October 2026

今日 语音ww库存没了,明天早上9点上新号

❤1

Signed 纽约接码【主号】@ribenapp

13 Sept 2026, 05:31 UTC≈1,030 viewsread 31 October 2026

最新通知:防止密码泄露,会员账号和子账号 必须要定期更改网址密码!!!请立即对密码进行更新(有子账号的通知子账号)

Signed 纽约接码【主号】@ribenapp

Showing the 12 most recent of 20 posts we hold for @ribenappsms. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“日本接码语音 记事本” (@ribenappsms), 1,109 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/ribenappsms.

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.