TITLESCREEN

Harukanaru Toki no Naka de 3 / release r0vx8dv8

Harukanaru Toki no Naka de 3 PlayStation 2, JP

Game
Harukanaru Toki no Naka de 3
Platform
PlayStation 2
Market
JP
Released
2004-12 4 sources agree
Publisher
Koei 4 sources agree
Developer
Ruby Party 1 agrees · 2 differ
Genre
Adventure 1 agrees · 2 differ
Players
up to 1 one source
Serial
SLPM-65834 SLPM-65849 SLPM-65850 SLPM-66005 SLPM-66128 SLPM-66345 SLPM-66688
Media
dvd
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.

Harukanaru Toki no Naka de 3 (Japan) redump

Identity
4cf12e43ce829bee37f8d86cee1e5647dc2a1f30 sha1, 3,115,188,224 bytes
Serial
SLPM-65834 SLPM-66688
1 file
FileSizeCRC32SHA-1MD5
Harukanaru Toki no Naka de 3 (Japan).iso3,115,188,224352c74394cf12e43ce829bee37f8d86cee1e5647dc2a1f30a68033cbdc53abe84eab217494e3a4eb

Harukanaru Toki no Naka de 3 (Japan) (Premium Box) redump

Identity
fb6b000808d538446f61b237f56c0493912243a4 sha1, 3,115,188,224 bytes
Serial
SLPM-65850 SLPM-66128 SLPM-66345
1 file
FileSizeCRC32SHA-1MD5
Harukanaru Toki no Naka de 3 (Japan) (Premium Box).iso3,115,188,22485133894fb6b000808d538446f61b237f56c0493912243a4aa26f473fc9ecf2df7fad3a9acc30351

Harukanaru Toki no Naka de 3 (Japan) (SLPM-65849) redump

Identity
c51052534934a9a7e41286c2deaf198cb14f32cd sha1, 3,115,188,224 bytes
Serial
SLPM-65849 SLPM-66005
1 file
FileSizeCRC32SHA-1MD5
Harukanaru Toki no Naka de 3 (Japan) (SLPM-65849).iso3,115,188,2244ff42530c51052534934a9a7e41286c2deaf198cb14f32cd34d981b3883eaeb95c82fbed14dcad26

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