Channel
@lokicalls
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
8subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001612951321 |
|---|---|
| Type | Channel |
| Username | @lokicalls |
| Created | Between 1 November 2021 and 19 November 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lokicalls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:31 | 8 | no change |
| 7 Aug 2026, 12:08 | 8 | first reading |
20 posts held, back to 19 November 2021 — 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 24 December 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
Measured directly from 1 video 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.
Free $SNOWY airdrop on injective. 100% airdrop allocation. Just complete the steps with this tg bot. U can download keplr wallet to get an injective address. https://t.me/injsnowy_bot?start=1547215078
satellite doge. Up 10x since i mentioned here. And we got guys like this shilling it. I personally would not fade but dyor im just a degen and not an advisor. https://x.com/1goonrich/status/1738029468919193804?s=46&t=8vOdWdFa21nU6ryX1bRTmA
Haven't called in a bit. But here's what I've bought lately Satellite Doge-1 on ETH currently 1.6M mcap https://www.dextools.io/app/en/ether/pair-explorer/0x4dad2532f1b6a8349ef0b7c08f4f4ac2d2870ef6 $WOLF on Avax Currently at 14m mcap https://www.dextools.io/app/en/avalanche/pair-explorer/0x08db8eafeea89476bfc51b07613f430748ff350a $WIF dogwifhat on Sol Currently at 65m mcap. Going crazy, pumped a lot. Wait for entr…
Update on Q*. Now dipped to under 1m mcap. All it takes is one tweet. NFA
https://www.dextools.io/app/en/ether/pair-explorer/0x39705ff79f4e50c9d6a59393e3b73933938e2a30 $GROGE has meme potential. It's like $GROK and $DOGE had a baby. Risky play, has room for lots of X's. Currently belown 300k mcap
Congrats if you got in $Q*. This thing has legs. Currently at 5m+ mcap.
https://www.dextools.io/app/en/ether/pair-explorer/0x8b5778d7bce9cd3b222969ed3ee16445ea4393d6 Another day, another victory for the OG 🤓lol. Took profits, left a bit just in case
^ decent swing play so far. Still retaining good volume. at 900K+ mcap. It's an elon play btw. dyor
Lots of volume NFA DYOR https://www.dextools.io/app/en/ether/pair-explorer/0x8B5778d7bCE9CD3b222969Ed3EE16445Ea4393D6
Choose your fighter. Three Qstar coins doing well. 1.3m mcap: https://www.dextools.io/app/en/ether/pair-explorer/0x8B5778d7bCE9CD3b222969Ed3EE16445Ea4393D6 224K mcap: https://www.dextools.io/app/en/ether/pair-explorer/0xBE477482426eE93604061a36b50BDb4a308F280a 23K mcap: https://www.dextools.io/app/en/ether/pair-explorer/0x3d4176a40ac193681040cafbcd01465ade492383
wen moon
$DORK https://t.me/DORKcoin This retraced 50%. Good entry if u want. Based devs. DYOR NFA.
Showing the 12 most recent of 20 posts we hold for @lokicalls. 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.
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.
@lokicalls named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Loki's Calls” (@lokicalls), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/lokicalls.
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.