BIZTRAC BETA
COMPANY REGISTER PROFILE
826173262 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

MOWOM AS

Org. no. 826173262 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −94,000
Equity NOK 74.7m
Incorporated 2020
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−94k kr).

MOWOM AS is registered as a limited company in Asker, Akershus with organisation number 826173262. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investeringsvirksomhet samt hva dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −94,000
▲ +85 %
Equity
NOK 74.7m
▲ +7 %
Est. value
NOK 91.3m

Financial health · 2025

Liquidity
1280.27
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns MOWOM AS?

MOWOM AS
· NOK −94,000 profit

MOWOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOWOM AS own?

MOWOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MOWOM AS

Who owns MOWOM AS?

CARL-CHRISTIAN SEIERSTAD is the largest registered owner, with 100.0%.

Where is MOWOM AS based?

MOWOM AS has its business address in Vettre.

Property

Business address c/o Carl-Christian Seierstad Blakstad Bryggevei 19A, 1392 Vettre
Cadastral unit 3203-61/9/0/0
Building Enebolig · 1 unit

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.