SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.256 Stop Loss: 17.069 Take Profit 1: 15.850 Take Profit 2: 15.443
Signed FLS SIGNALS

Channel
@FLS_signals
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,384subscribers
+276 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001364023723 |
|---|---|
| Type | Channel |
| Username | @FLS_signals |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/FLS_signals |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 00:02 | 1,384 | -5 |
| 23 Aug 2026, 03:58 | 1,389 | -5 |
| 19 Aug 2026, 20:18 | 1,394 | +297 |
| 16 Aug 2026, 17:26 | 1,097 | -1 |
| 13 Aug 2026, 00:15 | 1,098 | -5 |
| 10 Aug 2026, 09:27 | 1,103 | -3 |
| 7 Aug 2026, 18:31 | 1,106 | -2 |
| 6 Aug 2026, 21:16 | 1,108 | first reading |
20 posts held, back to 11 May 2026 — 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 13 May 2026. An engagement rate over an empty window would be a number about nothing.
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.256 Stop Loss: 17.069 Take Profit 1: 15.850 Take Profit 2: 15.443
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.392 Stop Loss: 15.573 Take Profit 1: 16.802 Take Profit 2: 17.212
Signed FLS SIGNALS
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.212 Stop Loss: 17.022 Take Profit 1: 15.806 Take Profit 2: 15.401
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.242 Stop Loss: 15.430 Take Profit 1: 16.648 Take Profit 2: 17.054
Signed FLS SIGNALS
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.745 Stop Loss: 17.583 Take Profit 1: 16.327 Take Profit 2: 15.908
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 17.043 Stop Loss: 16.190 Take Profit 1: 17.469 Take Profit 2: 17.895
Signed FLS SIGNALS
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.860 Stop Loss: 17.703 Take Profit 1: 16.438 Take Profit 2: 16.017
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.880 Stop Loss: 16.036 Take Profit 1: 17.303 Take Profit 2: 17.725
Signed FLS SIGNALS
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 16.642 Stop Loss: 17.474 Take Profit 1: 16.226 Take Profit 2: 15.810
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 17.102 Stop Loss: 16.247 Take Profit 1: 17.529 Take Profit 2: 17.957
Signed FLS SIGNALS
SELL ALERT VVVUSDT.P Timeframe: 1M Entry Price: 17.533 Stop Loss: 18.409 Take Profit 1: 17.094 Take Profit 2: 16.656
Signed FLS SIGNALS
BUY ALERT VVVUSDT.P Timeframe: 1M Entry Price: 18.155 Stop Loss: 17.247 Take Profit 1: 18.609 Take Profit 2: 19.063
Signed FLS SIGNALS
Showing the 12 most recent of 20 posts we hold for @FLS_signals. 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 — 657,817 of 1,623,166entries 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.
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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“F L S A.I BUY | SELL” (@FLS_signals), 1,384 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/FLS_signals.
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.