BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSVINGER HANDELSEIENDOM AS

Org. no. 991414274 Limited company (AS) Ringerike Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.9m
Equity NOK 1.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

KONGSVINGER HANDELSEIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 991414274. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 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 3.7m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.9m
Equity
NOK 1.1m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns KONGSVINGER HANDELSEIENDOM AS?

AKA AS
KONGSVINGER HANDELSEIENDOM AS
NOK 3.7m rev. · NOK 2.9m profit

KONGSVINGER HANDELSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSVINGER HANDELSEIENDOM AS

Who owns KONGSVINGER HANDELSEIENDOM AS?

AKA AS is the largest registered owner, with 100.0%.

What is the revenue of KONGSVINGER HANDELSEIENDOM AS?

KONGSVINGER HANDELSEIENDOM AS had revenue of NOK 3.7m in 2024.

Where is KONGSVINGER HANDELSEIENDOM AS based?

KONGSVINGER HANDELSEIENDOM 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.