BIZTRAC BETA
Accounting and bookkeeping

HØILUND REGNSKAP AS

Org. no. 997420063 Limited company (AS) Lillestrøm Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 21.5m
Operating profit NOK 1.9m
Equity NOK 988,000
Incorporated 2011
Employees 18
Share capital NOK 100,000

HØILUND REGNSKAP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 997420063. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2011 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskapstjenester og konsulenttjenester innen økonomisk og administrativ rådgivning. Selskapet skal også kunne delta i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 21.5m
Operating profit
NOK 1.9m
Equity
NOK 988,000
Est. value
NOK 10.1m

Financial health · 2025

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

Who owns HØILUND REGNSKAP AS?

H4 HOLDING AS
HØILUND REGNSKAP AS
NOK 21.5m rev. · NOK 1.9m profit

HØILUND REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØILUND REGNSKAP AS

Who owns HØILUND REGNSKAP AS?

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

What is the revenue of HØILUND REGNSKAP AS?

HØILUND REGNSKAP AS had revenue of NOK 21.5m in 2025.

Who is the general manager of HØILUND REGNSKAP AS?

Ruth-Marie Høilund Ler is registered as general manager of HØILUND REGNSKAP AS.

Where is HØILUND REGNSKAP AS based?

HØILUND REGNSKAP AS has its business address in Lillestrøm.

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.