Telegram RegisterThe public register of Telegram
Telegram profile photo for Softfixx.com tested files

Channel

Softfixx.com tested files

@softfixx_tested_files

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

234subscribers

-7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002652468871
TypeChannel
Username@softfixx_tested_files
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 October 2026
Measurements held7
Confirmed unchanged2 times, most recently 29 October 2026
On Telegramt.me/softfixx_tested_files

Topic

Software piracy — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.

Growth

2332412377 August 2026 — 241 subscribers8 August 2026 — 241 subscribers28 August 2026 — 240 subscribers4 September 2026 — 238 subscribers26 September 2026 — 235 subscribers14 October 2026 — 233 subscribers22 October 2026 — 234 subscribers2347 August 202622 October 2026
7 measurements spanning 75 days, net -7. 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 232–242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Oct 2026, 02:41234+1
14 Oct 2026, 21:06233-2
26 Sept 2026, 15:01235-3
4 Sept 2026, 09:42238-2
28 Aug 2026, 23:06240-1
8 Aug 2026, 09:48241no change
7 Aug 2026, 15:23241first reading

Engagement

20 posts held, back to 25 August 2025 — 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 9 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2100.0%

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 2 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 2 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 25 August 2025 to 9 April 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

9 Apr 2026, 14:33 UTC273 viewsread 8 August 2026

https://rms01.realme.net/sw/RMX3868export_11_15.0.0.1300EX01_2025120219410000.zip RMX3868export_11_15.0.0.1300EX01_2025120219410000 Phone Name = NARZO 70 Pro 5G Project No = 23689

9 Apr 2026, 13:28 UTC286 viewsread 8 August 2026

Realme Narzo 90x 5G RMX5264export_11_15.0.2.841EX01_2026010620580202_PCB = 25731. https://rms01.realme.net/sw/RMX5264export_11_15.0.2.841EX01_2026010620580202.zip

14 Mar 2026, 03:43 UTC405 viewsread 8 August 2026

https://dfs-serverauto-in.allawnofs.com/dfs/25/05/09/b3d734dbcea146bf904ea1333d4e6c5e.zip RMX3870export_11_15.0.0.600EX01_2025041123490000 Phone Name = Realme P1 5G Project No = 23709

6 Mar 2026, 05:24 UTC453 viewsread 8 August 2026

Realme C55 RMX3710export_11_15.0.0.1103EX01_2025082621250000 [PCB = 226AF] https://rms01.realme.net/sw/RMX3710export_11_15.0.0.1103EX01_2025082621250000.zip

26 Feb 2026, 17:02 UTC451 viewsread 8 August 2026

Realme 13 Plus 5G RMX5000 PCB= 25679 RMX5000export_11_15.0.0.1370EX01_2026010914260000 DOWNLOAD LINK https://rms01.realme.net/sw/RMX5000export_11_15.0.0.1370EX01_2026010914260000.zip

26 Feb 2026, 17:02 UTC383 viewsread 8 August 2026

Realme Narzo 70 Turbo 5G RMX5003 PCB= 24703 RMX5003export_11_15.0.0.1370EX01_2026010914270000 DOWNLOAD LINK https://rms01.realme.net/sw/RMX5003export_11_15.0.0.1370EX01_2026010914270000.zip

26 Feb 2026, 17:02 UTC314 viewsread 8 August 2026

Realme P3 Pro 5G RMX5032 PCB= 24623 RMX5032export_11_15.0.0.1034EX01_2025112418160258 DOWNLOAD LINK https://rms01.realme.net/sw/RMX5032export_11_15.0.0.1034EX01_2025112418160258.zip

17 Feb 2026, 17:07 UTC342 viewsread 8 August 2026

Realme C85 Pro 5G Android 15 PCB= 25665 RMX555525665_15.0.2.740(EX01)_251031 👇 https://dfs-serverauto-in.allawnofs.com/dfs/25/11/18/ab0ab568750142838cf8a67f3c50e88b.zip

17 Feb 2026, 16:29 UTC331 viewsread 8 August 2026

Realme 16 Pro+ 5G Android -16 PCB=25689 RMX5131export_11_16.0.2.412EX01_2026011816400000 👇 https://rms01.realme.net/sw/RMX5131export_11_16.0.2.412EX01_2026011816400000.zip

17 Feb 2026, 16:25 UTC312 viewsread 8 August 2026

Realme 16 Pro+ 5G ANDROID 16 RMX5131export_11_16.0.2.412EX01_2026011816390000_PCB = 25688 👇 https://rms01.realme.net/sw/RMX5131export_11_16.0.2.412EX01_2026011816390000.zip

17 Feb 2026, 16:17 UTC304 viewsread 8 August 2026

Realme C55 RMX3710export_11_15.0.0.1103EX01_2025082 Android 15 PCB = 226AD 👇 https://rms01.realme.net/sw/RMX3710export_11_15.0.0.1103EX01_2025082621220210.zip

15 Feb 2026, 11:38 UTC291 viewsread 8 August 2026

Realme Narzo 90x 5G RMX5264export_11_15.0.2.841EX01_2026010620580202_PCB = 25631 👇 https://rms01.realme.net/sw/RMX5264export_11_15.0.2.841EX01_2026010620580202.zip

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

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

“Softfixx.com tested files” (@softfixx_tested_files), 234 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/softfixx_tested_files.

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.