Telegram RegisterThe public register of Telegram
Telegram profile photo for ALL CALL SIGNS πŸ™πŸ™

Channel

ALL CALL SIGNS πŸ™πŸ™

@allcallsignsinfogroup

On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Citations Β· Cite this entry

360subscribers

-3 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-1001413608534
TypeChannel
Username@allcallsignsinfogroup
Created21 December 2020 β€” measured β€” cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/allcallsignsinfogroup

Topic

Local community β€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 81% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured β€” it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

360363361.56 August 2026 β€” 363 subscribers6 August 2026 β€” 363 subscribers15 August 2026 β€” 362 subscribers21 August 2026 β€” 363 subscribers28 August 2026 β€” 361 subscribers3 September 2026 β€” 360 subscribers6 August 20263 September 2026
6 measurements spanning 28 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between β€” snapshots are recorded only when a count changes, so gaps mean β€œno change observed”, never β€œinterpolated”. The vertical axis spans 360–363 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 10:07360-1
28 Aug 2026, 05:12361-2
21 Aug 2026, 06:28363+1
15 Aug 2026, 05:54362-1
6 Aug 2026, 21:31363no change
6 Aug 2026, 21:18363first reading

Engagement

20 posts held, back to 26 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 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 24 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

59 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 55.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ™3355.9%
❀813.6%
⚑610.2%
πŸ’”46.78%
🫑35.08%
😑23.39%
🀬23.39%
πŸ‘11.69%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities β€” πŸ™ is thanks in one channel and mourning in another β€” so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one β€” 4.34K, 1.2M β€” so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post β€” not by adding up the per-emoji breakdown above β€” those same posts carry 59 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 26 May 2026 to 24 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

24 Jul 2026, 07:03 UTC980 views2 reactionsread 6 August 2026
Photo

🚨 BEACON UPDATE: FOUND🚨 Russell from the Merseyside area, for whom we recently launched a beacon alert, has been located and is receiving support. Thank you to everyone who shared this post and helped bring about a positive result. #BeaconAlert #Found

πŸ‘1πŸ™1

23 Jul 2026, 07:11 UTCβ‰ˆ1,080 views4 reactionsread 6 August 2026
Photo

🚨 BEACON ALERT - MISSING VETERAN - SERIOUS CONCERNS FOR WELFARE 🚨 Have you seen Russell Brookes? There are serious concerns for Russell's welfare, and police are appealing for information to help locate him. Description: 43 β€’ 5'8" tall β€’ Medium build β€’ Short mousey-coloured hair β€’ Tribal tattoo on his left arm β€’ Large tattoo on his right calf β€’ Possibly wearing grey shorts and a light blue hooded top Last seen: R…

πŸ™3⚑1

17 Jul 2026, 05:59 UTC71 views3 reactionsread 6 August 2026
Forwarded from @shadowman2020Video

I’d like to ask a favour of all of you. Can you push this out to your followers on any social media platforms that you may have. I’m behind this push for October to be recognised as Veterans Month. I’m sick of seeing these lefty politicians alphabet people and the Islamists being recognised every day of the bloody year. No one is being asked for money, maybe if people can contribute big or small directly to the veter…

πŸ™3

8 Jul 2026, 08:46 UTCβ‰ˆ1,210 views5 reactionsread 6 August 2026
Photo

Jane has been located and is safe. Thank you to everyone who shared our alert.πŸ™πŸ™

❀2πŸ™2⚑1

8 Jul 2026, 05:39 UTCβ‰ˆ1,090 views2 reactionsread 6 August 2026
Photo

BEACON ALERT MISSING VETERAN Jane Todd is missing with serious concerns for her wellbeing, after leaving her home in the North Shields area on Sunday night 05/07. Her family say Jane booked a taxi, but they do not know which taxi company she used or where she was travelling to, but believe she may have been going somewhere to watch the England game. Her phone is turned off, and she is not receiving calls, texts or Wh…

⚑1πŸ™1

6 Jul 2026, 18:29 UTCβ‰ˆ1,190 views6 reactionsread 6 August 2026
Photo

🚨 BEACON UPDATE FOUND 🚨 We've received an update that Scott from Dorset has been located and is safe. Thank you to everyone who shared this alert and helped bring about a positive result.

❀3πŸ™2⚑1

3 Jul 2026, 21:10 UTCβ‰ˆ1,230 views2 reactionsread 6 August 2026
Photo

🚨 BEACON ALERT MISSING VETERAN 🚨 There are serious concerns for the welfare of Scott Yates, 45, who has been reported missing. Last Known Location: Blandford Forum, Dorset Last Contact: 24 June Scott does not have access to a vehicle but is known to travel using public transport, including trains, and may also accept lifts. If you have seen Scott, or have any information that could help locate him, please contac…

πŸ™2

29 Jun 2026, 16:27 UTCβ‰ˆ1,220 views4 reactionsread 6 August 2026
Photo

Photo, posted without a caption

❀3πŸ™1

28 Jun 2026, 11:18 UTCβ‰ˆ1,310 views4 reactionsread 6 August 2026
Photo

Daniel from Taunton has been reported safe by Avon & Somerset Police. Thank you to everyone who helped bring about a positive result.

πŸ™3⚑1

27 Jun 2026, 21:04 UTCβ‰ˆ1,250 views2 reactionsread 6 August 2026
Photo

Photo, posted without a caption

πŸ™2

Showing the 12 most recent of 20 posts we hold for @allcallsignsinfogroup. 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

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 3 September 2026 β€” this entry's latest reading, not the date you are reading this.

β€œALL CALL SIGNS πŸ™πŸ™β€ (@allcallsignsinfogroup), 360 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/allcallsignsinfogroup.

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.