7 May 2024, 19:15 UTC≈2,090 viewsread 6 August 2026
inSure DeFi is featured at Consensus! Like ❤️ and Share! https://twitter.com/ProficientPR/status/1787885361017811401
Channel
inSure DeFi Channel
@insuretoken
On this record: Growth · Engagement · Posts · Citations · Cite this entry
532subscribers
-1 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 | -1001207691077 |
|---|---|
| Type | Channel |
| Username | @insuretoken |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/insuretoken |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 04:57 | 532 | -1 |
| 6 Aug 2026, 21:01 | 533 | no change |
| 6 Aug 2026, 20:53 | 533 | first reading |
Engagement
20 posts held, back to 30 March 2023 — 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 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 20 posts for this entry, the most recent from 7 May 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
26 Mar 2024, 10:59 UTC≈1,850 viewsread 6 August 2026
https://x.com/DexCheck_io/status/1772569806119780540
29 Feb 2024, 00:19 UTC≈1,390 viewsread 6 August 2026
$SURE 🚀🚀🚀is looking very strong lately! Thank you all for your support and help in spreading the word on social media!
9 Feb 2024, 12:13 UTC≈1,350 viewsread 6 August 2026
https://x.com/InsureToken/status/1755902810934182053?s=20
7 Feb 2024, 20:33 UTC≈1,130 viewsread 6 August 2026
https://x.com/BlLife_Forum/status/1755206820904288749?
31 Jan 2024, 20:11 UTC907 viewsread 6 August 2026
https://x.com/insuretoken/status/1752747343554687199
28 Jan 2024, 20:18 UTC739 viewsread 6 August 2026
https://x.com/insuretoken/status/1751653230247903520
6 Jan 2024, 07:54 UTC731 viewsread 6 August 2026
https://x.com/InsureToken/status/1743459287479763183?s=
15 Dec 2023, 19:09 UTC755 viewsread 6 August 2026
https://x.com/insuretoken/status/1735730382450966533
15 Dec 2023, 03:16 UTC624 viewsread 6 August 2026
https://x.com/insuretoken/status/1734966435456151883
23 Oct 2023, 20:04 UTC755 viewsread 6 August 2026
https://x.com/web3globalmedia/status/1716527787316482372?s=20
10 Sept 2023, 20:19 UTC894 viewsread 6 August 2026
Please make sure you always self-custody your assets! Not your keys = not your crypto!
Showing the 12 most recent of 20 posts we hold for @insuretoken. 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.
Citation-graph rank
Citation-graph rank — 538,827 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 3 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“inSure DeFi Channel” (@insuretoken), 532 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/insuretoken.
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.