TITLESCREEN

SOCOM - U.S. Navy SEALs - Tactical Strike / release rr9zyzdw

SOCOM - U.S. Navy SEALs - Tactical Strike PlayStation Portable, US

Game
SOCOM - U.S. Navy SEALs - Tactical Strike
Platform
PlayStation Portable
Market
US
Released
2007-11-23 3 sources agree · title match
Publisher
Sony Computer Entertainment Europe 1 agrees · 2 differ · title match
Developer
Slant Six Games 3 sources agree · title match
Genre
Shooter 1 agrees · 2 differ
Players
up to 4 one source · title match
Serial
UCUS-98649 UP9000-NPUG80220_00-SOCOMTACTISTRIKE
Media
umd
Class
Commercial

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 - Tactical Strike (USA) no-intro

Identity
8ad0ca6b7f478e8440024a067b95f013e62cecd0 set1 of 2 files, 2,762,735,616 bytes
Serial
UCUS-98649 UP9000-NPUG80220_00-SOCOMTACTISTRIKE
2 files
FileSizeCRC32SHA-1MD5
SOCOM - U.S. Navy SEALs - Tactical Strike (USA).iso1,381,367,8089263533e93ed41e584f3de093bcb23b3451b0400b6ec6aacdbec03d2a0bf6f918443d0425ea0ae40
SOCOM - U.S. Navy SEALs - Tactical Strike (USA).iso1,381,367,808e913b94a633d8491907dc77998c7f953adae3ab8082e44dc02b601400c3ba83da907156b5f0e6eff

SOCOM - U.S. Navy SEALs - Tactical Strike (USA) redump

Identity
93ed41e584f3de093bcb23b3451b0400b6ec6aac sha1, 1,381,367,808 bytes
fp1
059821bb779ad9cf8dea481d3687c1cbda9e8f94
Serial
UCUS-98649
1 file
FileSizeCRC32SHA-1MD5
SOCOM - U.S. Navy SEALs - Tactical Strike (USA).iso1,381,367,8089263533e93ed41e584f3de093bcb23b3451b0400b6ec6aacdbec03d2a0bf6f918443d0425ea0ae40

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