biztrac. BETA
COMPANY REGISTER PROFILE
915912974 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

AKTIVT REGNSKAP AS

Org. no. 915912974 Limited company (AS) Herøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 62,000
Equity NOK 695,000
Incorporated 2015
Share capital NOK 30,000

AKTIVT REGNSKAP AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 915912974. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Regnskapsføring og økonomisk-/adminstrativ rådgivning, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 62,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▲ +7 %
Operating profit
NOK 62,000
▲ +137 %
Equity
NOK 695,000
▲ +11 %
Est. value
NOK 667,000

Financial health · 2025

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
6.7%
Satisfactory
Return on total assets
Solidity
50.8%
Very good
Equity as a share of total capital

Who owns AKTIVT REGNSKAP AS?

AKTIVT REGNSKAP AS
NOK 3.2m rev. · NOK 62,000 profit

AKTIVT REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKTIVT REGNSKAP AS

Who owns AKTIVT REGNSKAP AS?

June Anita Vågsholm Rooney is the largest registered owner, with 100.0%.

What is the revenue of AKTIVT REGNSKAP AS?

AKTIVT REGNSKAP AS had revenue of NOK 3.2m in 2025.

Who is the general manager of AKTIVT REGNSKAP AS?

June Anita Vågsholm Rooney is registered as general manager of AKTIVT REGNSKAP AS.

Where is AKTIVT REGNSKAP AS based?

AKTIVT REGNSKAP AS has its business address in Fosnavåg.

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.