Channel
@toruoikawaslove
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 8 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003953700339 |
|---|---|
| Type | Channel |
| Username | @toruoikawaslove |
| First recorded | 8 November 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/toruoikawaslove |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 02:22 | 1 | no change |
| 8 Nov 2026, 01:47 | 1 | first reading |
2 posts held, back to 28 May 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 2 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 November 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.
🐏🐏🐏🐏🐏☺️апп - ☺️ист 🐏 • ⛓️💌 — эдсофи , @thehunterkisser (Эден + шейр > зеркально) • 🔎🎃 — соллэйсы , @solssignificantother (соливан бругмансия + ноншейринг) • 🎻🌼 — лукачаён , @lukasmademoiselle (Лука + миррор-селектив) • 🦉💤 — оюнлайлы , @laylasdream (лайла + шейр) • ⚰🪷🦌 — лочасанядлеры , @luochadlerkisser (лоча + адлер + ноншейр) • 🧪🪼 — джонвайты , @jdhsangel (джон дейви харрис + ноншейр) • 🐙🐚— азулджи , @azul_kisser …
Channel created
Showing the 2 most recent of 2 posts we hold for @toruoikawaslove. 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.
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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“:33” (@toruoikawaslove), 1 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/toruoikawaslove.
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.