BIZTRAC BETA
Other education activities

SOMA MILJØKONSULT AS

Org. no. 980339955 Limited company (AS) Ullensaker Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 215,000
Operating profit NOK 193,000
Equity NOK 30,000
Incorporated 1998
Share capital NOK 30,000

SOMA MILJØKONSULT AS is registered as a limited company in Ullensaker, Akershus with organisation number 980339955. The business is classified under other education activities (NACE 85.597). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å stå for rådgivning, opplæring og undervisning innen følgende områder: helse, miljø, sikkerhet og kvalitetssikring.”. The most recent filed accounts, for the 2025 financial year, show NOK 215,000 in revenue and NOK 193,000 in operating profit.

Key figures · 2025

Revenue
NOK 215,000
Operating profit
NOK 193,000
Equity
NOK 30,000
Est. value
NOK 650,000

Financial health · 2025

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

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

Who owns SOMA MILJØKONSULT AS?

MORTEN HENRIK SOMA
SOMA MILJØKONSULT AS
NOK 215,000 rev. · NOK 193,000 profit

SOMA MILJØKONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOMA MILJØKONSULT AS

Who owns SOMA MILJØKONSULT AS?

MORTEN HENRIK SOMA is the largest registered owner, with 100.0%.

What is the revenue of SOMA MILJØKONSULT AS?

SOMA MILJØKONSULT AS had revenue of NOK 215,000 in 2025.

Who is the general manager of SOMA MILJØKONSULT AS?

Morten Henrik Soma is registered as general manager of SOMA MILJØKONSULT AS.

Where is SOMA MILJØKONSULT AS based?

SOMA MILJØKONSULT AS has its business address in Jessheim.

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.