BIZTRAC BETA
Business and other management consultancy activities

EVALIA AS

Org. no. 998933056 Limited company (AS) Steinkjer Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −200,000
Equity NOK 1.1m
Incorporated 2012
Share capital NOK 30,000

Signals

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

EVALIA AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 998933056. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgiving og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −200,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −200,000
Equity
NOK 1.1m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns EVALIA AS?

JO SAKARIASSEN
EVALIA AS
NOK 0 rev. · NOK −200,000 profit

EVALIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EVALIA AS own?

EVALIA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EVALIA AS

Who owns EVALIA AS?

JO SAKARIASSEN is the largest registered owner, with 100.0%.

What is the revenue of EVALIA AS?

EVALIA AS had revenue of NOK 0 in 2025.

Where is EVALIA AS based?

EVALIA AS has its business address in Steinkjer.

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.