LoTW and eQSL QSOs not matched by RUMLogNG

[N8XMS]

I have had a few QSOs downloaded from LoTW and eQSL that RUMLog claims do not match any in my log but they should be there. Everything about the QSOs matches perfectly except for the recorded times which has been a few minutes different - 12 minutes or so with an extreme case of a 33 minute difference in recorded time. What is the amount of flexibility that RUMLog uses in matching QSO times? With the possibility of one person recording the QSO time at the start of the contact and the other person recording it at the end of the contact I would think that a margin of +/- 60 minutes would be OK.

Thanks,
Paul - N8XMS

[DL2RUM]

LoTW and equals are using two different scenarios.
For eqsl, the QSO time is the time from the log of the worked station. A time difference of +/- 10 minutes is accepted. I could expand this time slot, but other problems could arise when you have made multiple QSO with the same station, due to mode enumeration changes in eqsl (mostly digital).

For LoTW confirmations, exact the same time of your own uploaded log will be returned. Normally, there should never be a difference. Some loggers may not log the seconds, thats why RUMlog will not take the seconds into consideration, but the minutes have to match.

[N8XMS]

Interesting! That would explain the two "not in log" QSOs that I had from eQSL but it doesn't explain the one from LoTW. The LoTW website shows the QSO in my account but RUMLog claimed that it wasn't in my log even though I can search and find it in my RUMLog log. (It was a QSO with JE1REU from 1999 so it had been uploaded by me to LoTW a long time ago from a different software package, but apparently just recently uploaded by JE1REU at his end.) It's not a significant issue since checking the QSO manually only took a moment. I'll keep monitoring to see if anything like this happens again.

Thanks and 73,
Paul - N8XMS