BIZTRAC BETA
Accounting and bookkeeping

ØKONOMISERVICE AS

Org. no. 976597613 Limited company (AS) Porsanger Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 1.9m
Equity NOK 19.2m
Incorporated 1996
Employees 8
Share capital NOK 100,000

ØKONOMISERVICE AS is registered as a limited company in Porsanger, Finnmark with organisation number 976597613. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1996 and has 8 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Bedriftsrådgivning og regnskapskontor samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 1.9m
Equity
NOK 19.2m
Est. value
NOK 21.0m

Financial health · 2024

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

Who owns ØKONOMISERVICE AS?

ANNE KARI IVERSEN
ØKONOMISERVICE AS
NOK 10.1m rev. · NOK 1.9m profit

ØKONOMISERVICE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ØKONOMISERVICE AS own?

ØKONOMISERVICE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ØKONOMISERVICE AS

Who owns ØKONOMISERVICE AS?

ANNE KARI IVERSEN is the largest registered owner, with 60.0%.

What is the revenue of ØKONOMISERVICE AS?

ØKONOMISERVICE AS had revenue of NOK 10.1m in 2024.

Who is the general manager of ØKONOMISERVICE AS?

Anne Kari Iversen is registered as general manager of ØKONOMISERVICE AS.

Where is ØKONOMISERVICE AS based?

ØKONOMISERVICE AS has its business address in Lakselv.

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.