BIZTRAC BETA
Accounting and bookkeeping

KS-KONTROLL AS

Org. no. 931703889 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 3,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KS-KONTROLL AS is registered as a limited company in Oslo, Oslo with organisation number 931703889. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forvaltning og drift av IT-systemer for regnskapsførere, revisorer, og andre aktører som er pålagt antihvitvaskingsloven. Yte konsulenttjenester, rådgivning, opplæring, og verktøy for fagområder som virksomhetsstyring, internkontroll, risikostyring og internrevisjon. Selskapet kan investere i andre virksomheter og i fast eiendom av enhver art.”.

Key figures · 2025

Operating profit
NOK −21,000
Equity
NOK 3,000
Est. value
NOK 5,000

Financial health · 2025

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 KS-KONTROLL AS?

3M SOLUTIONS AS
KS-KONTROLL AS
· NOK −21,000 profit

KS-KONTROLL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KS-KONTROLL AS er morselskap for 3 datterselskaper:

Frequently asked questions about KS-KONTROLL AS

Who owns KS-KONTROLL AS?

3M SOLUTIONS AS is the largest registered owner, with 100.0%.

Who is the general manager of KS-KONTROLL AS?

Noah David Johansen is registered as general manager of KS-KONTROLL AS.

Where is KS-KONTROLL AS based?

KS-KONTROLL AS has its business address in Oslo.

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.