BIZTRAC BETA
Accounting and bookkeeping

REGNSKAPSHUSET BORG AS

Org. no. 922364184 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 16.4m
Operating profit NOK 2.8m
Equity NOK 291,000
Incorporated 2019
Employees 11
Share capital NOK 30,000

REGNSKAPSHUSET BORG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922364184. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Økonomisk rådgivning, bokføring, investeringsvirksomhet og konsulentvirksomhet og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.4m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 16.4m
Operating profit
NOK 2.8m
Equity
NOK 291,000
Est. value
NOK 13.3m

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.6%
Weak
Equity as a share of total capital

Who owns REGNSKAPSHUSET BORG AS?

BORG FORVALTNING AS
REGNSKAPSHUSET BORG AS
NOK 16.4m rev. · NOK 2.8m profit

REGNSKAPSHUSET BORG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REGNSKAPSHUSET BORG AS

Who owns REGNSKAPSHUSET BORG AS?

BORG FORVALTNING AS is the largest registered owner, with 50.0%.

What is the revenue of REGNSKAPSHUSET BORG AS?

REGNSKAPSHUSET BORG AS had revenue of NOK 16.4m in 2024.

Who is the general manager of REGNSKAPSHUSET BORG AS?

Øyvind Hågenstad Ranum is registered as general manager of REGNSKAPSHUSET BORG AS.

Where is REGNSKAPSHUSET BORG AS based?

REGNSKAPSHUSET BORG AS has its business address in Trondheim.

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.