Channel
@robininuglobal
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001623204392 |
|---|---|
| Type | Channel |
| Username | @robininuglobal |
| Created | 5 February 2022 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/robininuglobal |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:02 | 1 | no change |
| 7 Aug 2026, 06:56 | 1 | first reading |
18 posts held, back to 5 February 2022 — 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 18 posts for this entry, the most recent from 12 August 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 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.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
📣I'm thrilled to announce you @RugFreeBot 🤖- A telegram bot that can help you scan any BSC/ETH/Polygon token at one click. This bot will automatically check for important owner privileges and give you a report within a second.🛡️ Currently BSC, Polygon and ETH is supported, but we're working on adding more... We're working on adding more more features as well. 👷♂️ #DYOR Start the bot here: https://t.me/rugfreebot I…
@RugFreeBot helps you scan a contract for possible rugpull or honeypot in advance before they scam you for free... So always scan you before invest. T.me/rugfreebot
Be Smart You get 100% free reviews of the projects What else do you want? Request the review by sending telegram group of project at @rugfreeroom
If you wanna get a project reviewed, just drop the project info on t.me/RugFreeRoom Or tag @rugfreeplanet on Twitter along with project Twitter handle
@RugFreePlanet is trying to make the Crypto space safer by reviewing the projects for free... Get your favorite project rated now for free T.me/RugFreePlanet
@RugFreePlanet is trying to make the Crypto space safer by reviewing the projects for free... Get your favorite project rated now for free T.me/RugFreePlanet
@RugFreePlanet is trying to make Bsc Space safer by reviewing the projects and giving crypto sc related updates They have already identified some projects as rugpulls (which were later confirmed rugpulls), (They're not a call channel or a token, just doing it for free
@RugFreePlanet is trying to make Bsc Space safer by reviewing the projects and giving crypto sc related updates They have already identified some projects as rugpulls (which were later confirmed rugpulls), (They're not a call channel or a token, just doing it for free
When an average scam rate of an influencer called bsc project is more than 90-95%, we reduced this risk to less than 10% Go Subscribe @RugFreePlanet if you love your hardly earned money
@RugFreePlanet is trying to make Bsc Space safer by reviewing the projects and giving crypto sc related updates They have already identified some projects as rugpulls (which were later confirmed rugpulls), (They're not a call channel or a token, just doing it for free
@RugFreePlanet is trying to make the Crypto space safer by reviewing the projects for free... Get your favorite project rated now for free T.me/RugFreePlanet
Showing the 12 most recent of 18 posts we hold for @robininuglobal. 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“This project was a Rug” (@robininuglobal), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/robininuglobal.
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.