biztrac. BETA
COMPANY REGISTER PROFILE
993021814 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Auditing

ØKOSERVICE AS

Org. no. 993021814 Limited company (AS) Gol Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 462,000
Equity NOK 1.0m
Incorporated 2008
Share capital NOK 100,000

ØKOSERVICE AS is registered as a limited company in Gol, Buskerud with organisation number 993021814. The business is classified under auditing (NACE 69.201). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Revisjon, regnskapsføring, rådgivning og økonomitjenester samt virksomhet naturlig relatert til dette, herunder investeringer i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 462,000 in operating profit.

Former names: REVISORSENTERET HALLINGDAL AS

Key figures · 2025

Revenue
NOK 3.9m
▲ +23 %
Operating profit
NOK 462,000
▼ −64 %
Equity
NOK 1.0m
▼ −5 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
14.4%
Good
Return on total assets
Solidity
33.1%
Good
Equity as a share of total capital

Who owns ØKOSERVICE AS?

ØKOSERVICE AS
NOK 3.9m rev. · NOK 462,000 profit

ØKOSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

ØKOSERVICE AS er morselskap for 1 datterselskap:

Frequently asked questions about ØKOSERVICE AS

Who owns ØKOSERVICE AS?

AUSAND AS is the largest registered owner, with 99.0%.

What is the revenue of ØKOSERVICE AS?

ØKOSERVICE AS had revenue of NOK 3.9m in 2025.

Who is the general manager of ØKOSERVICE AS?

Morten Flaget is registered as general manager of ØKOSERVICE AS.

Where is ØKOSERVICE AS based?

ØKOSERVICE AS has its business address in Gol.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.