Telegram RegisterThe public register of Telegram

Channel

JetSwan

@JetSwan

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

160subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002111926703
TypeChannel
Username@JetSwan
DescriptionZeitdokumente des Widerstandes E-Mail-Kontakt: JetSwan@gmx.net
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/JetSwan

Growth

1608 Aug 2026, 00:28 — 160 subscribers8 Aug 2026, 17:16 — 160 subscribers8 Aug 2026, 00:288 Aug 2026, 17:16
2 measurements taken within a single day. 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 159–161 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:16160no change
8 Aug 2026, 00:28160first reading

Engagement

13 posts held, back to 27 May 2026the 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 13 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7,170
Videos
64
Links
1,050

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 21s
Average length
47s

Measured directly from 3 videos 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.

Reaction mix

79 reactions across 13 posts, in 12 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🕊2936.7%
1721.5%
👍810.1%
🔥56.33%
😱45.06%
👏33.80%
😁33.80%
🤡33.80%
👌22.53%
🙈22.53%
🥰22.53%
👎11.27%

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 13 of the 13 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 79reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 27 May 2026 to 29 June 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

29 Jun 2026, 19:43 UTC88 views8 reactionsread 8 August 2026
Forwarded from @tomdabassmanVideo

Irgendetwas irritiert mich an diesem Clip, aber ich komm nicht drauf. https://x.com/i/status/2071674216265478412

🤡3😁3🙈2

27 Jun 2026, 08:08 UTC91 views2 reactionsread 8 August 2026
Forwarded from @VeranstaltungenPhoto

Wir machen eine Friedensreise, bitte teilen, damit viele Menschen miteinander sprechen für den Frieden #So2806 #BB #Cottbus #SN #Dresden #Mo2906 #SN #Leipzig #ST #Halle #Di3006 #ST #Magdeburg #NI #Braunschweig #Mi0107 #NI #Hannover #HB #Bremen #Do0207 #HH #Hamburg #SH #Lübeck #Fr0307 #MV #Rostock #Schwerin #Sa0407 #SH #Kiel #NI #Cuxhaven #So0507 #HB #Bremerhaven #NI #Oldenburg #Mo0607 #NI #Osnabrück #NW #Mün

🥰2

20 Jun 2026, 19:31 UTC121 views8 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊52🔥1

20 Jun 2026, 19:31 UTC110 views8 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊43🔥1

20 Jun 2026, 19:31 UTC88 views7 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊42🔥1

20 Jun 2026, 19:31 UTC85 views8 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊43🔥1

20 Jun 2026, 19:30 UTC90 views8 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊43👌1

20 Jun 2026, 19:30 UTC76 views7 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊42👌1

20 Jun 2026, 19:30 UTC85 views7 reactionsread 8 August 2026
Photo

#DOGSFORPEACE ❤️🐶🕊️ Dresden, 20/06/2026 https://t.me/JetSwan

🕊42🔥1

13 Jun 2026, 17:43 UTC104 views2 reactionsread 8 August 2026
Photo

„Mahnwache für Palästina“ Bremen, Domtreppen 13/06/2026 https://t.me/JetSwan

👏2

13 Jun 2026, 17:41 UTC108 views1 reactionsread 8 August 2026
Photo

„Mahnwache für Palästina“ Bremen, Domtreppen 13/06/2026 Jeden Samstag von 11:30 bis 12:30 Uhr findet eine „Mahnwache für Palästina“ an den Domtreppen in Bremen statt. Diese regelmäßige Mahnwache ist bis Anfang 2027 angekündigt. https://t.me/JetSwan #FreePalestine #Bremen #Mahnwache #FriedenStattKrieg

👏1

6 Jun 2026, 10:09 UTC115 views8 reactionsread 8 August 2026
Forwarded from @EvaHermanOffiziellVideo

. „Massive Attack schlägt Alarm! Bei ihren aktuellen Live-Shows scannt die Band das Publikum per KI-Gesichtserkennung in Echtzeit. Die Gesichter landen auf der Leinwand – im Look der Überwachungssoftware von Palantir. Ein genialer, düsterer Protest gegen Massenüberwachung!“ https://x.com/AldousHuxIey/status/2062750971151753458 JETZT abonnieren und nichts mehr verpassen: https://t.me/EvaHermanOffiziell

👍8

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

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“JetSwan” (@JetSwan), 160 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/JetSwan.

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.