Load title from database based on member country
Formatting

Your code has some formatting issues, reducing the readability of it:


spacing: your spacing around = seems arbitrary and you are missing spaces around ..
indentation: 2 spaces aren't really enough, use at least 4.
you should also indent the queries after a linebreak a bit more to increase readability.
your curly brackets are not consistent.


Security

Depending on who can add members and ranks, you may be vulnerable to XSS as the name is echoed unencoded. Even if this isn't a problem now because only you can add them, your requirements may change. Encoding input is always a good idea.

Also, depending on the type and changability of id you may be vulnerable to SQL injection. Always use prepared statements.

Structure

You should add functions to increase the maintainability - readability, reusability, changability, etc - of your code. 

For example, selectMembersByCountry($country) or selectMemberRanksByID($id), which would then return an array of members and/or ranks.

Naming

zeile isn't a good name. First of all, your variable names shouldn't switch languages, and ideally they should all be in English. 

But row wouldn't be much better. What is it really? Well, $result contains a list of members, right? So its name could reflect that, and then zeile could be member, which would give you: $member = $membersResult-&gt;fetch_assoc().

Simplify SQL

You could put all the logic directly into the query, but I don't think that that is necessary, so I'll leave that to someone else (although you may want to change your table structure first, see below).

I would say that it's fine the way it is. Especially when you extract the queries to functions, you would have well-defined and reusable functions. 

Putting all the logic directly in the query is likely to be less readable and harder to maintain, and I doubt that it will give you a noticeable performance benefit (definitely not if you limit by 2). 

Table Structure


Why do your mapping tables have their own id? This doesn't seem necessary. 
For a 1:n relationship, you don't actually need a mapping table.
member-country doesn't actually seem to be a 1:n relationship, but n:m; A member can have multiple countries, and a country can have multiple members.
Because of the last point, you actually have duplications in your country2memb table (multiple entries of US for example). What you should do is have  a member table, a country table, and a memberCountry table to map between them.