BIZTRAC BETA
COMPANY REGISTER PROFILE
889274972 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

MOSSIN HOLDING AS

Org. no. 889274972 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Equity NOK 140,000
Incorporated 2005
Share capital NOK 100,000

MOSSIN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 889274972. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selskapets formål er å investere i andre selskap.”.

Key figures · 2025

Equity
NOK 140,000
▲ +0 %
Est. value
NOK 228,000

Financial health · 2025

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

Who owns MOSSIN HOLDING AS?

MOSSIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOSSIN HOLDING AS own?

MOSSIN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOSSIN HOLDING AS

Who owns MOSSIN HOLDING AS?

CHRISTIN SILVER MOSSIN is the largest registered owner, with 100.0%.

Where is MOSSIN HOLDING AS based?

MOSSIN HOLDING AS has its business address in Bergen.

Property

Business address c/o Mossin Fosswinckels gate 18B, 5007 Bergen
Cadastral unit 4601-164/1408/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 9 units

5 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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