Are you in contact with “the IT guys” of your company about your use of Syncthing to sync data on company drives?
I am asking because A you should, and B the easiest way to find out is to ask them something like “Hey, I am going to sync some 10s of GiBs of data using Syncthing, can you check whether that has any effects on the company network and if so what they are please?”.
Syncthing generally uses either TLS over TCP or TLS wiggled into UDP (IETF QUIC). TLS is the same encryption protocol used for https - major differences between https and sycnthing are
the port number used (443/https, vs 22000/syncthing) [assuming default settings].
The certificates used in the crypto handshake look a bit different from what you would expect in https and syncthing’s certs all read “syncthing” in the Common Name. Note that certificates in TLS 1.3 cannot be seen by a passive wire-listener.
The crypto handshake is also slightly different, for example because syncthing normally uses ALPN, which would read “http/X” in https and reads “bep/1.0” in syncthing.
There are some other minor differences here and there that I haven’t listed here.
But apart from the things mentioned above, syncthing traffic “is just TLS” and thus looks a lot like https.
Sorry, but you have to explain what you are trying to achieve.
Can you explain how one drive traffic looks like? What about your remote desktop traffic?
To be honest, it seems like a pointless question to ask unless you can explain a reason behind it. Also, if you are not the one looking after the networks, why do you even care? If people have questions, they will come to you and ask whatever they deem relevant.