BIZTRAC BETA
COMPANY REGISTER PROFILE
934657551 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Site preparation

SILENT CATCH AS

Org. no. 934657551 Limited company (AS) Stad Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 21,000
Incorporated 2024
Share capital NOK 30,000

SILENT CATCH AS is registered as a limited company in Stad, Vestland with organisation number 934657551. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Undervannsentreprenørtjenester: yrkesdykking. Turistguide: skipper (fører båt med turister), divemaster/dykkerleder (guider turister under vann), fiskeguide (guider turister på fisketurer), andre turisttjenester (nordlysturer og trugeguiding). Sjåfør: transport av opptil 8 turister.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 21,000
Est. value
NOK 9,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SILENT CATCH AS?

JOHN HANSEN SCHNEIDER
SILENT CATCH AS
NOK 0 rev. · NOK 0 profit

SILENT CATCH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILENT CATCH AS

Who owns SILENT CATCH AS?

JOHN HANSEN SCHNEIDER is the largest registered owner, with 100.0%.

What is the revenue of SILENT CATCH AS?

SILENT CATCH AS had revenue of NOK 0 in 2024.

Where is SILENT CATCH AS based?

SILENT CATCH AS has its business address in Stadlandet.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.