16 Jan 2025, 06:54 UTC265 viewsread 12 August 2026
Photo
✅ LONG #FET Entry: now - 1.3531 SL: 1.3233 (2.2%) TP: 1.4 - 1.4491 Lev: x10 vol: x5
Channel
HEY! LOOK AT ME - 0.1 BTC to 100 BTC
@heylookme
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002172268505 |
|---|---|
| Type | Channel |
| Username | @heylookme |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/heylookme |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:19 | 7 | no change |
| 11 Aug 2026, 17:15 | 7 | first reading |
Engagement
20 posts held, back to 6 December 2024 — 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 20 posts for this entry, the most recent from 16 January 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 62
- Links
- 1
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.
Recent posts
14 Jan 2025, 09:57 UTC38 viewsread 12 August 2026
Photo
✅ BUY SPOT #FET Entry: 1.2835 SL: 1.1362 (11.5%) TP: 1.8
14 Jan 2025, 09:56 UTC34 viewsread 12 August 2026
Photo
✅ LONG #MORPHO #BITGET Entry: now - 2.5075 SL: 2.4129 (3.77%) TP: 2.6 - 2.7 - 2.8 Lev: x5 vol: x5 -------------------------------------------- Anh em yêu quý thì ủng hộ Kurt và Chipmunk tại BingX I Bitget | MEXC Kurt cảm ơn mọi người
7 Jan 2025, 04:19 UTC127 viewsread 12 August 2026
Photo
After breaking through the 1.43 level, $FET is currently in an upward trend and is supported by SonicR. Some AI agents have started to increase for the next wave, so I believe $FET will continue to rise after consolidating here. ▸ Technical analysis shows bullish signals ▸ Hot trend: AI Agents Send it 🚀
3 Jan 2025, 07:23 UTC98 viewsread 12 August 2026
Photo
😭 SHORT $BTC Entry: 97137.23 STL: 97893.10 TP: 94693.90
26 Dec 2024, 02:47 UTC86 viewsread 12 August 2026
Photo
😭 SHORT $BTC Entry: now STL: 100.017,02 TP: 97.600 - 95.636.82 - TP is your choice
24 Dec 2024, 04:53 UTC46 viewsread 12 August 2026
Photo
✅ Long #SOL Entry: now - 190.1 SL: 185.3 (2.7%) TP: 196.7 - 206
19 Dec 2024, 13:37 UTC20 viewsread 12 August 2026
😁 Lệnh từ sáng mà đến giờ không khớp nên thôi hủy nhé anh em!
19 Dec 2024, 03:18 UTC17 viewsread 12 August 2026
Photo
✅ LONG #DOGE Entry: 0.35220 STL : 0.34005 TP: 0.37787 - 0.38858
18 Dec 2024, 02:24 UTC53 viewsread 12 August 2026
Photo
✅ Buy Limit #XAU Entry: 2639.51 STL : 2635.37 TP: 2646 - 2654.87
17 Dec 2024, 10:15 UTC47 viewsread 12 August 2026
Photo
Vàng chờ mua lên thôi
12 Dec 2024, 02:30 UTC78 viewsread 12 August 2026
Photo
✅ Short Limit #BTC Entry: 100945.58 STL : 101372.71 TP: 99638.65
Showing the 12 most recent of 20 posts we hold for @heylookme. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“HEY! LOOK AT ME - 0.1 BTC to 100 BTC” (@heylookme), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/heylookme.
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.