I think this is happening as NV0E is not a WRL user, if you search his callsign on QRZ it shows he is in CO. So the entry in your log is correct, what is incorrect however is the data in your second image and i think thats where the disconnect is.
You have a qrz subscription and are using the qrz callsign lookup so you are getting accurate data in your logbook when logging qso’s.
Where the incorrect data is coming from is when you do a search for a callsign through the WRL search bar IF the callsign is not a WRL member. I think this is due to that data being pulled from hamdb which has been increasingly inaccurate here lately. We are working on finalizing our own internal callsign lookup database that will have the majority of the same data as QRZ and will show the results accurately.
I’ll reach out to the team and see if we can go ahead and at least swap over the search bar results to our internal database or come up with another solution so there is not mis-matched information being shown like in this case.
I hope this helps explain what/why this is happening.
I just wanted to touch base and let you know we’ve fixed this for you. Once we launch out internal database which will have all the updated data this wont be an issues anymore. Sorry for the trouble!