The answer before the background

Our recommendation

Use this Mini Survival Zombie Fight wiki page as a source directory, not as an anonymous claim dump. The strongest identity sources are Apple app ID 6462363666, Google Play package com.hdsoul.minisurvival.android under BitStrong Games, the separate current package com.hdsoul.minisurvival, and the BitStrong company site. The official descriptions confirm shelter service buildings, survivor professions, sentry defense, at least four islands, farming, fishing, equipment crafting, bosses, pets and more than 80 zombie or monster types. Version, package, currency, event and connectivity claims must be labelled separately rather than merged.

Start every fact with the exact product

EntityVerified identifierBest use
Apple editionApp ID 6462363666; seller BitStrong Pte. Ltd.iPhone/iPad compatibility, IAP disclosure and version history.
BitStrong Android editioncom.hdsoul.minisurvival.androidPublisher support, Android/Windows store availability and current listing facts.
Separate Android entitycom.hdsoul.minisurvivalCurrent alternative package facts; do not silently merge saves or entitlements.
PublisherBITSTRONG PTE. LTD.Company identity and official contact trail.
Developer communityFacebook /minisurvivalgame and developer-listed DiscordDated announcements that still require package and version labels.

What the official descriptions support

  • Shelter buildings include restaurants, hospitals, hotels and gas stations that provide services and income.
  • Survivors have professional and combat abilities and can work in facilities, sentry positions or exploration teams.
  • The map includes at least four islands and named environments such as outskirts, forests, farmland and downtown areas.
  • Food comes from crops, fruit, fishing and exploration; materials support equipment crafting and facility upgrades.
  • Bosses, mutated creatures, pets and more than 80 visually distinct zombies or monsters are part of the advertised game.

Do not erase update history

The Apple listing records version 1.2.0 on July 30, 2025 and earlier 1.1.x updates. That history includes a new map and sign-in system, seasonal events, SSR characters, Boss Challenge Tournament, Endless Tower Challenge and a partner fragment exchange shop. These features should be cited with their version date, not described as launch-day or universal facts.

Google Play currently shows different package identities and fetched update dates. A database row should therefore include platform, package, publisher, version, region, observation date and source URL. If two rows disagree, preserve both until the developer or live client resolves the difference.

Use a claim template that another reader can audit

For a recipe, survivor, building, boss, currency or event, record the exact in-client name, platform, package, version, menu or map location, input, output and observation date. Add a screenshot only when it preserves those fields. Translation variants should point to one entity rather than becoming separate mechanics.

For a code, mod, trainer or generator claim, require a first-party source and a safe verification path. The absence of a publisher source must be stated. Link to the dedicated safety pages rather than reproducing executable instructions, passwords or unverified download mirrors.

Common questions

Is there one official community wiki?

No first-party wiki was identified in the checked sources. This page therefore acts as a sourced directory and labels community evidence separately.

Which app identity should I record?

Record the store, app or package ID, publisher, version and region. The two current Android package IDs should not be treated as automatically interchangeable.

What systems are confirmed by official descriptions?

Shelter services, survivor roles, sentry defense, four or more islands, farming, fishing, crafting, bosses, pets and 80-plus zombie or monster types.

How should an old event fact be written?

Attach the platform, version and date from the update history. Do not change the article date and present an old seasonal feature as currently active.

What we checked

Official listings establish current availability and product facts. Community pages are used for mechanics and build history, then labeled separately.