BIZTRAC BETA
Accounting and bookkeeping

AASEN & ELSVATN REGNSKAP AS

Org. no. 920282806 Limited company (AS) Hattfjelldal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 29,000
Equity NOK 430,000
Incorporated 2018
Share capital NOK 30,000

AASEN & ELSVATN REGNSKAP AS is registered as a limited company in Hattfjelldal, Nordland with organisation number 920282806. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av regnskapskontor, regnskapsføring for andre, og deltakelse i andre virksomheter ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 29,000
Equity
NOK 430,000
Est. value
NOK 414,000

Financial health · 2025

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

Who owns AASEN & ELSVATN REGNSKAP AS?

ARNFINN AASEN
AASEN & ELSVATN REGNSKAP AS
NOK 1.3m rev. · NOK 29,000 profit

AASEN & ELSVATN REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AASEN & ELSVATN REGNSKAP AS

Who owns AASEN & ELSVATN REGNSKAP AS?

ARNFINN AASEN is the largest registered owner, with 70.0%.

What is the revenue of AASEN & ELSVATN REGNSKAP AS?

AASEN & ELSVATN REGNSKAP AS had revenue of NOK 1.3m in 2025.

Who is the general manager of AASEN & ELSVATN REGNSKAP AS?

Arnfinn Aasen is registered as general manager of AASEN & ELSVATN REGNSKAP AS.

Where is AASEN & ELSVATN REGNSKAP AS based?

AASEN & ELSVATN REGNSKAP AS has its business address in Hattfjelldal.

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.