Telegram RegisterThe public register of Telegram
Telegram profile photo for DS Group | Safety & Amazon Relay

Channel

DS Group | Safety & Amazon Relay

@dsgservices

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

118subscribers

+8 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-1001691230593
TypeChannel
Username@dsgservices
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/dsgservices

Growth

109118113.57 August 2026 — 110 subscribers7 August 2026 — 109 subscribers9 August 2026 — 109 subscribers15 August 2026 — 113 subscribers22 August 2026 — 118 subscribers7 August 202622 August 2026
5 measurements spanning 15 days, net +8. 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 108–119 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 19:38118+5
15 Aug 2026, 15:42113+4
9 Aug 2026, 07:46109no change
7 Aug 2026, 22:33109-1
7 Aug 2026, 19:28110first reading

Engagement

18 posts held, back to 2 June 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.

ERR · 30 days
205.6%
avg views ÷ 118 subscribers
Avg views / post
243
3 posts measured
Reaction rate
4.12%
reactions ÷ views · ER floor
Posts in window
3
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held18 (2 June 202629 July 2026)
Views total728
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 07:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

299 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 31.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9331.1%
🔥9030.1%
🤝5016.7%
155.02%
👏134.35%
🙏113.68%
💯72.34%
🎉62.01%
41.34%
31.00%
🏆20.669%
👀20.669%
🤔20.669%
❤‍🔥10.334%

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

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

29 Jul 2026, 19:39 UTC426 views10 reactionsread 9 August 2026
Photo

🚨 Amazon Relay Is Working on a New Onboarding Process Amazon is developing a new onboarding experience that is expected to make Relay applications more thorough. The new process may include: • Government ID verification • More owner and business information • Additional compliance checks • Enhanced insurance and bank account verification This means stricter reviews, more personal information required, and a highe

3👀2🔥2🤔2💯1

27 Jul 2026, 17:24 UTC143 views11 reactionsread 9 August 2026
Photo

📌 Amazon Relay Approved After Initial Rejection ✅ Another successful case completed by DS Group. Our client's initial Amazon Relay application was rejected. We reviewed the case, corrected the issues, and handled the reapplication process. 🎉 Result: Application successfully approved — the carrier is now ready to haul with Amazon Relay. #AmazonRelay

👍43🤝3🎉1

24 Jul 2026, 17:24 UTC159 views9 reactionsread 9 August 2026
Photo

📌 Amazon Relay Payment Hold Released ✅ Another successful case completed by DS Group. Our client needed to change their bank account in Amazon Relay while a significant amount of funds remained on hold. Our team handled: • Amazon Relay bank account change • Case escalation • Communication with Amazon Relay • Follow-up until resolution 🎉 Result: The bank account was successfully updated, and $152,891.88 in held pa

👍4🔥3🏆2

20 Jul 2026, 15:38 UTC134 views18 reactionsread 9 August 2026
Photo

📌 Violation Successfully Transferred ✅ Another successful DataQs case completed. We helped our client transfer a violation to the correct motor carrier by preparing the required documentation and working directly with the reporting agency. 🎉 Result: The DataQs challenge was approved, and the carrier information was corrected. Protecting our clients' safety records through accurate compliance support. #ViolationT

🎉5👍5🔥5🤝3

15 Jul 2026, 09:31 UTC191 views18 reactionsread 9 August 2026
Photo

📌 Amazon Relay Application Approved ✅ Another successful Amazon Relay approval for our client. Our team managed the entire application process—from document preparation and compliance review to submission and approval. 🎉 Result: The carrier is now approved and ready to haul loads through Amazon Relay. Helping carriers get approved faster with a smooth and compliant application process. #AmazonRelay

💯6👍5🔥5👏2

3 Jul 2026, 21:10 UTC251 views20 reactionsread 9 August 2026
Photo

📌 Another FMCSA Audit Successfully Passed ✅ Another client successfully passed their FMCSA Safety Audit. The FMCSA auditor confirmed that all requested documentation was accurate, compliant, and complete, resulting in a PASS with positive feedback. Our team provided: • Audit preparation • Compliance documentation review • Safety file organization • Full audit support 🎉 Result: FMCSA Safety Audit – PASSED. Helpi

🔥6👍5🙏5🤝21❤‍🔥1

29 Jun 2026, 18:56 UTC207 views14 reactionsread 9 August 2026
Photo

📌 From Company Formation to Amazon Relay Approval ✅ Another carrier successfully launched from scratch. We handled the entire process from start to finish: • Company formation • USDOT & MC registration • Compliance setup • Amazon Relay application 🎉 Result: The company is fully operational and approved to haul with Amazon Relay. From startup to approval—we take care of every step. #AmazonRelay

👍4👏4🔥3🤝3

14 Jun 2026, 19:03 UTC275 views21 reactionsread 9 August 2026
Photo

✅ SUCCESSFUL AUDIT PASS The carrier missed its FMCSA audit request and its operating authority was revoked. We helped reactivate the authority, prepared the required documentation, and successfully guided the company through the audit process. 📋 Result: PASS Another carrier is back in compliance and operating legally. #FMCSA

👍7🔥7🤝7

11 Jun 2026, 14:49 UTC274 views21 reactionsread 9 August 2026
Photo

📌 Amazon Relay Approval After Rejection ✅ We helped our client successfully reapply for Amazon Relay after the initial application was rejected. After reviewing and correcting the application, our team resubmitted the case and secured approval. 🎉 Result: Amazon Relay account approved and ready to operate. #AmazonRelay

🔥8🤝7👍6

7 Jun 2026, 16:39 UTC277 views18 reactionsread 9 August 2026
Photo

📌 Amazon Relay Approval After Initial Rejection ✅ Another successful Amazon Relay activation for our client. The carrier's initial Amazon Relay application was rejected. Our team reviewed the case, identified the issues, prepared the required documentation, and guided the carrier through the reapplication process. Services provided: • Application review and compliance assessment • Issue identification and resolut

🔥5🤝5👍4👏2🙏2

6 Jun 2026, 05:54 UTC262 views19 reactionsread 9 August 2026
Photo

🚨 UNSAFE DRIVING — How to Lower Your CSA Score One trick not many people know 👇 Increase your truck & driver count on FMCSA before the monthly Snapshot Date. Same violations. Lower score. Update your fleet count in MCS-150 before the snapshot — and your UNSAFE DROVING score drops automatically. 📅 Snapshot dates are the 3rd or last Friday of every month. Check the exact schedule here: 👉 https://csa.fmcsa.dot.gov/

👍6🔥54🙏4

3 Jun 2026, 13:27 UTC328 views18 reactionsread 9 August 2026
Photo

📢 MOTUS System Update The rollout of the new MOTUS platform continues to create challenges for many carriers across the industry. Commonly reported issues include: • Identity verification delays or failures • Inability to claim company accounts • Long wait times for FMCSA support • Delayed responses to support tickets and case requests • Delays in insurance companies updating coverage filings through MOTUS • Extend

🔥8👍5👏5

Showing the 12 most recent of 18 posts we hold for @dsgservices. 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 August 2026 — this entry's latest reading, not the date you are reading this.

“DS Group | Safety & Amazon Relay” (@dsgservices), 118 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/dsgservices.

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.