# Are R(T)node frequencies rounded by default?

_Help · started by welo on Wed, Jun 10, 2026 8:29 AM_

Tags: LoRa

---

## Original post

**welo** · Wed, Jun 10, 2026 8:29 AM

I have some rnodes connected to a host as well as rtnode nodes in the field, which are at the very specific frequency of 869431250 and 869493750 (see https://rns.recipes/forum/help/high-bandwidth-vs-high-range-lora-tradeoff-for-setting-up-a-large-swarm-of-rtnodes for the reasoning of that) but in every website tracking interface announcements this the values are always rounded to the 10khz [see example](https://rns.fyi/?mode=all&hide_dead=false&q=long+range&selected=c7cc7cc76dc3632569b7b84022de11f7&selected_class=rnode&selected_interface=6f6f7865345eb131213934f3b62c4f1c9fb5790bb347e5ff4b196ab9ff70a80c) and after doing some more research I can see that even with rnstatus -D the interfaces have their frequencies rounded to the closest 10khz so it's not a limitations on any of these sites but the announcements themselves have this truncated value.

My question is, is it just the announcements are rounded to the closest 10khz and the actually lora rnode modules are actually listening at the frequencies mentioned above or is everything rounded to 10khz when you enter the values into either standard RNS or RTnode and that the announcements are simply showing the true frequency the devices are listening. I'm way more concerned about the first case, from my knowledge on how Lora works if the frequency was off by 4khz it would still probably work with a high spreading factor but it is certainly not ideal and would mean anyone casually trying to connect to any of my nodes using the interface announcement stream would be out of phase by up to 5khz which is probably bad.

---

## Reply 1

**welo** · Fri, Jun 12, 2026 6:53 PM

I think it's rounded by default after some testing cause I communicate from an rnode with a frequency of 869431250 to one that is 869431000, though the difference is so small that it's hard to tell.

Also it's actually rounded by 1khz not by 10khz so this is less of an issue than I originally thought.

---