BIZTRAC BETA
Rental and operating of own or leased real estate

KALLERUD HANDELSPARK AS

Org. no. 992779489 Limited company (AS) Ringerike Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 21.1m
Operating profit NOK 15.6m
Equity NOK 123.5m
Incorporated 2008
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KALLERUD HANDELSPARK AS is registered as a limited company in Ringerike, Buskerud with organisation number 992779489. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 1.0m, divided into 1005980 shares. The company's stated purpose is: “Å eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.1m in revenue and NOK 15.6m in operating profit.

Key figures · 2024

Revenue
NOK 21.1m
Operating profit
NOK 15.6m
Equity
NOK 123.5m
Est. value
NOK 118.4m

Financial health · 2024

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

Who owns KALLERUD HANDELSPARK AS?

HANDELSEIENDOMMER ØST AS
KALLERUD HANDELSPARK AS
NOK 21.1m rev. · NOK 15.6m profit

KALLERUD HANDELSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KALLERUD HANDELSPARK AS

Who owns KALLERUD HANDELSPARK AS?

HANDELSEIENDOMMER ØST AS is the largest registered owner, with 100.0%.

What is the revenue of KALLERUD HANDELSPARK AS?

KALLERUD HANDELSPARK AS had revenue of NOK 21.1m in 2024.

Where is KALLERUD HANDELSPARK AS based?

KALLERUD HANDELSPARK AS has its business address in Hønefoss.

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.