What you're looking for is often called "siblings".
When sharing the same Taxonomy terms there are Contextual filters
Has taxonomy term that can be used and this can work in a lot of cases.
But there are cases even with shared Taxonomy that needs to go a different route (possibly when using Aggregation or Multilingual sites). That second "sibling" route is also what you need to use when the connection is done through an Entity Reference field that isn't Taxonomy, like it is in your case.
The solution is done with the help of two Relationships and one Contextual filter.
Create the Content type Views showing Admin nodes. You first add the Relationship for your ER Location field, this introduces info about the referenced node into the Views. In your case this is the info about Location node referenced from Admin nodes.
Then you add the reverse Relationship to the first one, it will use the first Relationship by default, this is where the matching happens. The second Relationship introduces info about the content that is using that ER field. In your case this is all the Activity nodes that point to the same Location.
Add the Contextual filter for Node ID and make it use the second Relationship. Set it the usual way, default value and ID from URL, validate against Activity Content type.
If this is a Block Display set it to display in a theme region on Activity nodes and adjust its Contextual filter settings. Now when you visit an Activity node you will see listed all the Admin nodes that share the same Location ER.
Repeat the procedure for the second ER field Sport type. You will have 4 Relationships and 2 Contextual filters in the end. Don't build everything at once, test step by step and build it all for only one ER field first.
When building for the second ER field you can use the keyword
all in Views Preview to "shortcircuit" the first Contextual filter so you can test the second one directly, without interference from the first one (you enter values into Preview separated with
/ for each Contextual filter you have, for example
all/34 to bypass the first Contextual,
all/all to bypass both Contextuals, or
34/34 to test for the Activity node with the NID 34).
This answer has a bit more details for a similar example: Entity Reference widget selctor in view referring same reference