BIZTRAC BETA
Computer consultancy and computer facilities management activities

AASE CONSULTING AS

Org. no. 993129186 Limited company (AS) Hamar Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 519,000
Operating profit NOK 234,000
Equity NOK 4.9m
Incorporated 2008
Share capital NOK 100,000

AASE CONSULTING AS is registered as a limited company in Hamar, Innlandet with organisation number 993129186. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av konsulenttjenester og produkter innen innvevde datasystemer (Embedded Computers), investeringer i verdipapirer og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 519,000 in revenue and NOK 234,000 in operating profit.

Key figures · 2024

Revenue
NOK 519,000
Operating profit
NOK 234,000
Equity
NOK 4.9m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns AASE CONSULTING AS?

BJØRN ESPEN AASE
AASE CONSULTING AS
NOK 519,000 rev. · NOK 234,000 profit

AASE CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AASE CONSULTING AS own?

AASE CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AASE CONSULTING AS

Who owns AASE CONSULTING AS?

BJØRN ESPEN AASE is the largest registered owner, with 100.0%.

What is the revenue of AASE CONSULTING AS?

AASE CONSULTING AS had revenue of NOK 519,000 in 2024.

Where is AASE CONSULTING AS based?

AASE CONSULTING AS has its business address in Hamar.

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.