BIZTRAC BETA
Accounting and bookkeeping

ØKONOMI CONSULT AS

Org. no. 966847263 Limited company (AS) Eidsvoll Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 796,000
Operating profit NOK 480,000
Equity NOK 3.7m
Incorporated 1993
Share capital NOK 102,000

ØKONOMI CONSULT AS is registered as a limited company in Eidsvoll, Akershus with organisation number 966847263. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1993. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Regnskapsførsel, økonomisk rådgivning, samt investere i og yte finansiell bistad til datterselskaper og tilknyttede selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 796,000 in revenue and NOK 480,000 in operating profit.

Key figures · 2024

Revenue
NOK 796,000
Operating profit
NOK 480,000
Equity
NOK 3.7m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns ØKONOMI CONSULT AS?

AALBORG AAS HOLDING AS
ØKONOMI CONSULT AS
NOK 796,000 rev. · NOK 480,000 profit

ØKONOMI CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ØKONOMI CONSULT AS er morselskap for 3 datterselskaper:

Frequently asked questions about ØKONOMI CONSULT AS

Who owns ØKONOMI CONSULT AS?

AALBORG AAS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØKONOMI CONSULT AS?

ØKONOMI CONSULT AS had revenue of NOK 796,000 in 2024.

Who is the general manager of ØKONOMI CONSULT AS?

Ingun Aalborg Aas is registered as general manager of ØKONOMI CONSULT AS.

Where is ØKONOMI CONSULT AS based?

ØKONOMI CONSULT AS has its business address in Eidsvoll.

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.