This took some time to figure out and understand, even with the code at hand. :)
When you are running a manual/normal check, the site uses your premium state with geocaching.com. When running a verify the site uses the premium state of the target user. Reni-Chris is not a premium user. The consequence is that geocaches which are premium does not get their coordinates exposed to the LUA engine when running the verify-process.
I have added the following text in the DEV environment:
The tests will be run with the premium status of the target profile accounts, therefore coordinates for premium only geocaches won't be exposed to the challenge checker script if the profile is not premium.