Telegram RegisterThe public register of Telegram
Telegram profile photo for 欧洋无限收巴西出海流量

Channel

欧洋无限收巴西出海流量

@ou9166

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

5subscribers

+0 since we began measuring on 30 September 2026

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

Register entry

Telegram ID-1004380351262
TypeChannel
Username@ou9166
Description官方唯一账号 @ou916,双向机器人🤖 @ou916_bot
Created21 September 2026 — measured — dated from the channel’s first post
First recorded30 September 2026
Last confirmed live30 September 2026
Measurements held2
On Telegramt.me/ou9166

Growth

530 Sept 2026, 11:47 — 5 subscribers30 Sept 2026, 12:22 — 5 subscribers30 Sept 2026, 11:4730 Sept 2026, 12:22
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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 12:225no change
30 Sept 2026, 11:475first reading

Engagement

5 posts held, back to 21 September 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
330.0%
avg views ÷ 5 subscribers
Avg views / post
16.5
2 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
5
of 5 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 1 of 2 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 30 September 2026
Posts held5 (21 September 2026 – 30 September 2026)
Views total33
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 12: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.

Recent posts

30 Sept 2026, 09:56 UTC6 viewsread 30 September 2026

‼️【重要通知】‼️ 一、投放详悉 1.投放地区:巴西 2.投放媒体 :FB/TT 3.投放类型 :pwa 4.首充门槛 :10雷 5.开户时区 :-3时区 6.kpi要求 : 3条线,当天24小时roas(直推首充用户充值金额)要达到110%+ 7.事件:购物 8.每天需视频或者录屏核对当天的消耗 汇损按消耗多少算多少 必须老像素开V0 二、预算 1.测试周期3天,测试周期需次日结算。 2.测试期单线路预算500,实时roas达标可加预算,加预算务必有人在线提供实时消耗。(3天测试期内,超预算核减) 3.连续几天不达标这边也会关停。 4.如果起量了就根据前一天的消耗情况预付款,如果当晚量级突破预期,产生了小部分垫资次日下午结算。 5.瞬烧一律按照A结算或者核减至roas达标 四、其他重要事项: 1.日报要求统计广告账号面板数据和后台的数据,以后台为准。 2.日报次日北京时间14点更新后请先截图日报及广告消耗面板到群里…

30 Sept 2026, 07:15 UTCviews —

欧洋无限收巴西出海流量 pinned «‼️【重要通知】‼️ 一、投放详悉 1.投放地区:巴西 2.投放媒体 :FB/TT 3.投放类型 :pwa 4.首充门槛 :10雷 5.开户时区 :-3时区 6.kpi要求 : 3条线,当天24小时roas(直推首充用户充值金额)要达到110%+ 7.事件:购物 8.每天需视频或者录屏核对当天的消耗 汇损按消耗多少算多少 二、预算 1.测试周期3天,测试周期需次日结算。 2.测试期单线路预算500,实时roas达标可加预算,加预算务必有人在线提供实时消耗。(3天测试期内,超预算roas还没达标的情况下需核减至达标)…»

28 Sept 2026, 08:39 UTC27 views0 reactionsread 30 September 2026

‼️【重要通知】‼️ 一、投放详悉 1.投放地区:巴西 2.投放媒体 :FB/TT 3.投放类型 :pwa 4.首充门槛 :10雷 5.开户时区 :-3时区 6.kpi要求 : 3条线,当天24小时roas(直推首充用户充值金额)要达到110%+ 7.事件:购物 8.每天需视频或者录屏核对当天的消耗 汇损按消耗多少算多少 二、预算 1.测试周期3天,测试周期需次日结算。 2.测试期单线路预算500,实时roas达标可加预算,加预算务必有人在线提供实时消耗。(3天测试期内,超预算roas还没达标的情况下需核减至达标) 3.过了测试期,起量了这边不限制预算,但是roas必须达标,不达标的情况下需进行核减至达标,连续几天不达标这边也会关停。 4.如果起量了就根据前一天的消耗情况预付款,如果当晚量级突破预期,产生了小部分垫资次日下午结算。 5.瞬烧一律按照A结算或者核减至roas达标 三、素材 ✅ 高清爆奖视频为主,少量爆奖图片…

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

“欧洋无限收巴西出海流量” (@ou9166), 5 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/ou9166.

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.