Telegram RegisterThe public register of Telegram

Channel

TURANIX PROJECT

@TuranixCollaboration

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

5subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002484210564
TypeChannel
Username@TuranixCollaboration
CreatedBetween 1 September 2024 and 31 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/TuranixCollaboration

Growth

56 August 2026 — 5 subscribers13 August 2026 — 5 subscribers6 August 202613 August 2026
2 measurements spanning 6 days. 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
13 Aug 2026, 00:175no change
6 Aug 2026, 21:185first reading

Engagement

6 posts held, back to 31 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 6 posts for this entry, the most recent from 10 February 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

Lifetime counters from Telegram’s own channel header, read 13 August 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.

Recent posts

10 Feb 2025, 08:19 UTC34 viewsread 13 August 2026
Forwarded from @pearlsacheFile

🕷 BIG COLLABORATION THE WACKERS 🕷 present by: @thewackers 📷 SPECIAL TAG : @thewackers, @ofceldefeat, @OFCLILBARTO, @santaliez, @ladystead, @bertyies, @ofccibaye, @ofcbossquad, @OVERKILLOFC, @JobesOfc, @itsHookers, @swimfive, @wardoettpride, @ofcdesissy, @ofcpuffiecy, @ofcgorvez, @kopdarpride, @OFCPRUGAL, @ofcsensus, @piersonia, @jasdeisz, @KOBREKK, @berculley, @tracoxx, @ofcinfinite, @leucove, @OfcTuranix, @untoldr

5 Feb 2025, 11:21 UTC29 viewsread 13 August 2026
Forwarded from @ofcthemortalFile

ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤ ㅤ♡ ❍ ⌲ •• 𝗟𝗶𝗸𝗲𝗱 𝗯𝘆 @OFCTHEMORTAL and 9.304.999 others. ➿➿➿➿➿➿➿➿➿➿➿➿➿ ➥⛈FIRST TIME IMMORTAL COLLABORATION Big thanks to the squads who have participated in this collab, hopefully we can establish a good relationship in the future. and can establish good cooperation later hopefully we can meet in another collaboration. very special tag: @BAGINDAOFFICIAL @KANDJENGOFFICIAL @JOSGARCITY @o

31 Jan 2025, 08:58 UTC40 viewsread 13 August 2026
Forwarded from @ofcgorvezFile

ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤ ㅤ♡ ❍ ⌲ •• 𝗟𝗶𝗸𝗲𝗱 𝗯𝘆 @OFCGORVEZ and 3.789.999 others. ➥🌟 COLLABORATION GORVEZ thank you to partner for participating with us in our collaboration. ╰►✅Special Tag : @ofceldefeat, @ofcdesissy, @OfcTuranix, @ohsoker, @ladystead, @ofcsandforz, @ofcskindaz, @ofcthemoz, @thekarpol, @laskayefolks, @thegotex, @leucove, @kohlarprides, @lonsexstone, @OVERKILLOFC, @slatboys56, @tracoxx, @wardoe

Showing the 6 most recent of 6 posts we hold for @TuranixCollaboration. 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.

Forward network

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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“TURANIX PROJECT” (@TuranixCollaboration), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/TuranixCollaboration.

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.