BIZTRAC BETA
Child welfare services

OMSORG KONSULT AS

Org. no. 928357759 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 695,000
Operating profit NOK 127,000
Equity NOK −5,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).

OMSORG KONSULT AS is registered as a limited company in Drammen, Buskerud with organisation number 928357759. The business is classified under child welfare services (NACE 88.991). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester knyttet til barnevern og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 695,000 in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 695,000
Operating profit
NOK 127,000
Equity
NOK −5,000
Est. value
NOK 966,000

Financial health · 2025

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

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

Who owns OMSORG KONSULT AS?

KRISTA NORI BALABAN
OMSORG KONSULT AS
NOK 695,000 rev. · NOK 127,000 profit

OMSORG KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMSORG KONSULT AS

Who owns OMSORG KONSULT AS?

KRISTA NORI BALABAN is the largest registered owner, with 100.0%.

What is the revenue of OMSORG KONSULT AS?

OMSORG KONSULT AS had revenue of NOK 695,000 in 2025.

Who is the general manager of OMSORG KONSULT AS?

Krista Nori Balaban is registered as general manager of OMSORG KONSULT AS.

Where is OMSORG KONSULT AS based?

OMSORG KONSULT AS has its business address in Drammen.

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.