Channel
@unisig1as
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001312793724 |
|---|---|
| Type | Channel |
| Username | @unisig1as |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/unisig1as |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 20:03 | 2 | no change |
| 6 Aug 2026, 23:52 | 2 | first reading |
20 posts held, back to 21 September 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 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 19 February 2025. An engagement rate over an empty window would be a number about nothing.
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.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
(in reply to Universal signals) > ⚡⚡ #ADX/BTC ⚡⚡ > Exchanges: Huobi.pro, Binance… Binance #ADX/BTC Take-Profit target 3 ✅ Profit: 30.5399% 📈 Period: 1 Months 3 Days 22 Hours 32 Minutes ⏰
(in reply to Universal signals) > ⚡⚡ #ADX/BTC ⚡⚡ > Exchanges: Huobi.pro, Binance… Binance #ADX/BTC Take-Profit target 2 ✅ Profit: 8.058% 📈 Period: 1 Months 3 Days 22 Hours 28 Minutes ⏰
Guys , don't rush into spot trades. There are still 4 days remaining as per my timeframe Analysis for uncertainty. We will give some futures trades if we get opportunity. Spot trades are for holding hence please have patience for some better entries.
&14084448814#1264544566 (in reply to Universal signals) > Buy Bitcoin at 44100$ with 2% capital. > … If you didn't buy at 44100$ then only I recommend to buy now. If you have bought at 44100$ then wait for averaging. Those who didn't buy at 44100$ then you can only buy of 2% capital now. We can get opportunity to buy/average in next 6 days. Target is the same 72k$. There will be some fluctuations in between so you …
&14084448814#1264544566 (in reply to Universal signals) > Buy Bitcoin at 44100$ with 2% capital. > … Hold if you have bought at that. $72k will be done. Just we need to average at better price if BTC breaks below 40k$. Don't be scared. It's healthy correction which will lead towards new ATH. full &14084448814#1264544566
&14084448814#1264544566 Btc daily above 40000 then it's good. Breaking below is bad till 34200$ full &14084448814#1264544566
&14084448814#1264544566 (in reply to Universal signals) > Buy Bitcoin at 44100$ with 2% capital. > … Btw keep this one for target. We just closed of 40680$ , not the above. Holding that 2% capital in loss full &14084448814#1264544566
&14084448814#1264544566 (in reply to Universal signals) > #ICPUSDT > … Close #ICPUSDT in loss :( full &14084448814#1264544566
&14084448814#1264544566 (in reply to Universal signals) > #GRTUSDT > … Close GRT bid full &14084448814#1264544566
&14084448814#1264544566 If BTC breaks 40k then it will be too bearish daily close. Add bid at 34200$ full &14084448814#1264544566
&14084448814#1264544566 Please close the BTC buy order which was filled at 40680. Currently BTC is at 40300. full &14084448814#1264544566
Showing the 12 most recent of 20 posts we hold for @unisig1as. 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.
@unisig1as named 1 handle 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“unisig242d-uni” (@unisig1as), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/unisig1as.
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.