Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 why it has no browse page of its own yet.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views per post sit far above this size band
25,900 average views per post against 32,837 subscribers — an engagement rate of 78.7%. Across the 24,287 registered channels in the same cohort — 31,624–99,997 subscribers — the middle half sit between 2.63% and 15.1%, with a median of 6.83%.
What this was computed from
Window
30 days (24 August 2026 – 23 September 2026)
Posts measured
14 of 14 published in the window (0 exact, 14 rounded by Telegram)
Views totalled
361,900
Mature posts only
78.7% over 14 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 23 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
33 measurements spanning 42 days, net +1,047. 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 31,068–33,068 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
19 Sept 2026, 03:59
32,837
+1,538
16 Sept 2026, 20:18
31,299
-28
15 Sept 2026, 01:58
31,327
-16
13 Sept 2026, 12:59
31,343
-23
11 Sept 2026, 13:57
31,366
-35
8 Sept 2026, 21:41
31,401
-47
5 Sept 2026, 16:40
31,448
-12
3 Sept 2026, 16:00
31,460
-20
2 Sept 2026, 05:35
31,480
-19
1 Sept 2026, 02:35
31,499
-21
31 Aug 2026, 04:49
31,520
-10
30 Aug 2026, 02:11
31,530
-9
29 Aug 2026, 01:54
31,539
-13
28 Aug 2026, 02:13
31,552
-24
27 Aug 2026, 03:06
31,576
-9
26 Aug 2026, 00:34
31,585
-14
24 Aug 2026, 22:14
31,599
-36
23 Aug 2026, 10:45
31,635
-38
21 Aug 2026, 23:45
31,673
-23
20 Aug 2026, 19:35
31,696
first reading
Engagement
35 posts held, back to 24 February 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 72 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
80.6%
avg views ÷ 32,837 subscribers
Avg views / post
26,500
14 posts measured
Reaction rate
1.56%
reactions ÷ views · ER floor
Posts in window
14
of 35 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
Window
Rolling 30 days · latest post in window 20 September 2026
Posts held
35 (24 February 2026 – 20 September 2026)
Views total
370,400
Reactions total
5,778
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Sept 2026, 06:23 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
128
Videos
38
Links
66
Lifetime counters from Telegram’s own channel header, read 23 September 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
45s
Average length
11s
Measured directly from 4 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
22,226 reactions across 35 posts, in 14 distinct kinds. The most used accounts for 39.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
8,689
39.1%
🔥
7,127
32.1%
❤🔥
3,092
13.9%
😍
1,238
5.57%
🍌
672
3.02%
🌚
588
2.65%
🌭
317
1.43%
👀
182
0.819%
👍
94
0.423%
🤯
87
0.391%
💯
65
0.292%
😘
26
0.117%
😱
25
0.112%
🙈
24
0.108%
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 35 of the 35 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 22,226 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 24 February 2026 to 20 September 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.
Hola que hacen?
yo estoy aburrida nadie me escribe por mas que ponga mi telegram aca
https://t.me/rebeca_bareiro
❤37😍10❤🔥3🍌2🌭1
Showing the 12 most recent of 35 posts we hold for @onichanrebeccabareiro. 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.
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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“Rebecca bareiro / onichan paraguay 🔥” (@onichanrebeccabareiro), 32,837 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/onichanrebeccabareiro.
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.
