Unless you constrain the runlist it will be calculated at runtime. Determining this just by looking at the cookbook versions loaded into the server is very hard.
How does one constrain the runlist? One mechanism is to set the version explicitly on the run-list, but this will only partially help as it won't lock the versions of dependencies (unless you've added constraints in your cookbook metadata).
The best approach is to setup Chef environments and associate this with your managed nodes. Use tools to set the cookbook constraints when loading cookbooks. For example using Berkshelf
berks upload
berks apply my-special-runtime-env
Another lessor known approach is using the knife cookbook upload command
knife cookbook upload --all --force --environment my-special-runtime-env
Finally there the option of using the new chef policy file functionality. I have not personally used it, but include it for completeness.