TITLESCREEN

SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 / release rtxg03jn

SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 PlayStation Portable, EU

Game
SOCOM - U.S. Navy SEALs - Fireteam Bravo 2
Platform
PlayStation Portable
Market
EU
Released
2007-06-15 0 agree · 3 differ · correction
Publisher
Sony Computer Entertainment Europe 1 agrees · 2 differ · title match
Developer
Zipper Interactive 3 sources agree · title match
Genre
Third-person shooter 1 agrees · 1 differs · title match
Players
up to 16 one source · title match
Serial
ULET-00794/0.02
Media
umd
Class
Prototype

Identified copies

Each is an entry of a dump list (No-Intro, Redump, MAME, FBNeo, the MAME software lists) or a copy a scan read. A copy is identified by its identity hash whatever its file is called or packed in: see Identify.

SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 (Europe) (En,Fr,De,Es,It) (Beta) redump

Identity
0b5047b59ba0c7376fad9711b8db2d434e48fd83 sha1, 1,672,609,792 bytes
fp1
0040e94ccefbd996198d3b146c3e9f80d7d0bed2
Serial
ULET-00794/0.02
Languages
En,Fr,De,Es,It
1 file
FileSizeCRC32SHA-1MD5
SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 (Europe) (En,Fr,De,Es,It) (Beta) (2007-03-13).iso1,672,609,7929fe75df70b5047b59ba0c7376fad9711b8db2d434e48fd83743c52a2f52124d039e163c39ed9b08c

SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 (Europe) (En,Fr,De,Es,It) (Beta) (2007-03-13) redump

Identity
0b5047b59ba0c7376fad9711b8db2d434e48fd83 sha1, 1,672,609,792 bytes
Languages
En,Fr,De,Es,It
1 file
FileSizeCRC32SHA-1MD5
SOCOM - U.S. Navy SEALs - Fireteam Bravo 2 (Europe) (En,Fr,De,Es,It) (Beta) (2007-03-13).iso1,672,609,7929fe75df70b5047b59ba0c7376fad9711b8db2d434e48fd83743c52a2f52124d039e163c39ed9b08c

Evidence

The facts above were resolved from statements made by the sources, kept with where each came from and how it was joined to this copy. The marks beside each fact say how many sources state the published value and how many state another. Every statement, field by field · how facts are collected and resolved.

Suggest a correction when a fact above is wrong and you can show where the right one is written

JSON · evidence JSON