This looks like a poorly encoded name which was even more poorly decoded and reencoded.
Initially, the name seems to be:
A-Trust Ges. für Sicherheitssysteme im elektr. Datenverkehr GmbH
The name was then encoded in big-endian UTF-16. In this case, this means that every character yielded two bytes, the first of which having value 0.
Upon decoding, whatever did the decoding failed to recognize the string as UTF-16 (maybe it was wrongly tagged in the certificate; an UTF-16 string should be
BMPString but some cases of UTF-16 stuffed in
TeletexString have been spotted in the wild; see the X.509 style guide for more about it). The string was decoded as if it was ASCII, with "invalid" bytes represented with the C-style convention of "
\x" followed by two hexadecimal characters. This sequence is used in the C programming language to insert explicit byte values in literal strings. Therefore, the initial "
A-T" became "
\x00A\x00-\x00T". Similarly, "
für" became "
\x00f\x00\xFC\x00\xr" because "ü" is not an ASCII character, and has value 0xFC (aka 252) in Unicode.
When printing out the string, a further injury was inflicted on that string, namely the wholesale removal of all backslash characters. This yielded the exact string that you observe.
(Note that the EFF "CA map" shows other examples of this "C-style without backslashes" representation, e.g. "
SCEE - Sistema de CertificaxE7xE3o ElectrxF3nica do Estado", which really should be "SCEE - Sistema de Certificação Electrónica do Estado".)
Now a simple Googling points to, indeed, a commercial German CA called A-Trust. Now the mystery deepens a bit, because the CA Web site uses a certificate issued by the CA itself, and the root CA uses the name:
A-Trust Ges. f. Sicherheitssysteme im elektr. Datenverkehr GmbH, which is correctly encoded in the certificate (as an
UTF8String), but is not exactly the one you observe: the "
für" has been replaced with "
My guess is that what you see is a previous version of the root CA certificate from that CA, and it had encoding problems, which were "solved" by changing the text into something which is pure ASCII. I.e., instead of fixing their software to handle non-ASCII characters properly, they sidestepped the issue. That's kind of sloppy.