BIZTRAC BETA
Uoppgitt

DELTA RISK AS

Org. no. 987208147 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 2.6m
Equity NOK 1.9m
Incorporated 2004
Share capital NOK 100,000

DELTA RISK AS is registered as a limited company in Oslo, Oslo with organisation number 987208147. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Megling av skade- og personforsikring i næringsvirksomhet og offentlig forvalting i Norden og alt som skjer i forbindelse med dette, herunder rådgivning og skadebehandling samt investeringer i eiendom og andre bedrifter og alt som skjer i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 2.6m
Equity
NOK 1.9m
Est. value
NOK 8.3m

Financial health · 2024

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

Who owns DELTA RISK AS?

MORTEN WANG
DELTA RISK AS
NOK 4.7m rev. · NOK 2.6m profit

DELTA RISK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DELTA RISK AS own?

DELTA RISK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DELTA RISK AS

Who owns DELTA RISK AS?

MORTEN WANG is the largest registered owner, with 100.0%.

What is the revenue of DELTA RISK AS?

DELTA RISK AS had revenue of NOK 4.7m in 2024.

Who is the general manager of DELTA RISK AS?

Morten Wang is registered as general manager of DELTA RISK AS.

Where is DELTA RISK AS based?

DELTA RISK 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.