biztrac. BETA
COMPANY REGISTER PROFILE
934304640 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Refrigeration installation, heat pump installation and installation of fireplaces

HUNSBEDT EIENDOM AS

Org. no. 934304640 Limited company (AS) Kvinesdal Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

HUNSBEDT EIENDOM AS is registered as a limited company in Kvinesdal, Agder with organisation number 934304640. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å selge og montere varmepumper og rørleggertjenester, samt eie, leie og investere i eiendom og aksjer.”.

Former names: HUNSBEDT VARME OG RØR AS

Key figures · 2025

Operating profit
NOK −7,000
▲ +39 %
Equity
NOK 13,000
▼ −34 %
Est. value
NOK 13,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HUNSBEDT EIENDOM AS?

HUNSBEDT EIENDOM AS
· NOK −7,000 profit

HUNSBEDT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUNSBEDT EIENDOM AS

Who owns HUNSBEDT EIENDOM AS?

Kjell Inge Hunsbedt is the largest registered owner, with 100.0%.

Who is the general manager of HUNSBEDT EIENDOM AS?

Kjell Inge Hunsbedt is registered as general manager of HUNSBEDT EIENDOM AS.

Where is HUNSBEDT EIENDOM AS based?

HUNSBEDT EIENDOM AS has its business address in Kvinesdal.

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.