Channel
@okadaojo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
118subscribers
+10 since we began measuring on 15 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003937162237 |
|---|---|
| Type | Channel |
| Username | @okadaojo |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/okadaojo |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 03:27 | 118 | +1 |
| 27 Oct 2026, 04:37 | 117 | +1 |
| 20 Oct 2026, 11:28 | 116 | +3 |
| 12 Oct 2026, 16:20 | 113 | +2 |
| 2 Oct 2026, 11:22 | 111 | +2 |
| 17 Sept 2026, 00:40 | 109 | +1 |
| 15 Sept 2026, 11:22 | 108 | no change |
| 15 Sept 2026, 10:47 | 108 | first reading |
5 posts held, back to 13 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 15 September 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
来自速搜推荐 @SSOU 📢吃瓜 📢外围足球 世界杯足球 世... 📢芭提雅修车 芭提雅上门 📢皇冠体育🅰️亚星私网�... 📢皇冠百家乐 欧博百家乐 ... 📢PanSci 泛科学 📢🔥顶尖黑客|app逆向... 📢抖音精选搞笑视频 📢另一角度看世界👁 📢著名调查记者王志安 📢🏅速搜官方🏅｜🔥福... 📢欧博代理|亚星代理|亚星... 📢环球360|环球360代... 📢台灣本土極速外送茶推薦�... 📢亚星私网🅰️欧博私网�... 👉流量互推规则介绍💥 以下是广告推荐 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢⚽️注册送138🧧百家乐/棋牌/电竞体育信誉平台 📢🅾️免费试玩✅大客必备✅注册送158🅾️ ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 📢🔰开元官方🔥代理70%|电子棋牌|AG百家乐 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员，即可在
近期因为有人冒充潇湘阁修车 真实 潇湘阁 认准 这三个 ⚠️⚠️⚠️除此以外 都是假的 @XXGE8 ← 非-泰 等国 助理 @XXGE888 ← 新-马 等国 助理 @lxl168 ← 此号将慢慢不在接待 ↓ ↓ 导航频道 ↓ ↓ 极品越南 @manilapasay000 极品小菲 @manilapasay001 高中高端 @manilapasay002 日韩大洋马 @manilapasay003 潇 湘 阁 各国 在岗导航
中国🇨🇳新人， 兰宝宝 身高164 体重44 胸围C 年纪03 高情商，不挑客，啥客户都能接 短暂上班几天 快餐5万90分钟 6小时两次8万 过夜12小时3次13万
马尼拉中国🇨🇳 心心 ————————————————— ꒰・身高/Height ：162Cm ꒰・胸围/Bust ：C（真实） ꒰・体重/Weight： 45kg ꒰・年龄/age：04 暂停 短兼 喜欢【甜美 纯欲 单纯的必选款宝藏女孩】 【拿得出手的顶级🔝女友】 快餐 50000 小夜 80000 六小时二次 大夜 130000 十二小时三次
🦢 编号: Kiari （ Y88 ）🦢 🧊 国籍:🇵🇭菲律宾 🟢年龄: 18 🟢身高: 163cm 🟢体重: 39kg 🟢胸围: 32B 👑➗➗➗➗➗➗➗➗➗➗ 特点: 上新嫩妹、没有孩子/第一次下海/口交/共浴/按摩/白皮肤/亲吻/真胸/可以喝酒 💳➗➗➗➗➗➗➗➗➗➗ 💰 价格: 3小时 9000 /2次 8小时 16000/3-4次
Showing the 5 most recent of 5 posts we hold for @okadaojo. 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.
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.
Named by 7 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“马尼拉冈田修车 马尼拉冈田上门 马尼拉冈田越南 马尼拉冈田菲妹” (@okadaojo), 118 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/okadaojo.
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.