BIZTRAC BETA
Rental and operating of own or leased real estate

HUNTONIT EIENDOM AS

Org. no. 927730421 Limited company (AS) Vennesla Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 16.8m
Operating profit NOK 15.2m
Equity NOK 749,000
Incorporated 2021
Share capital NOK 391,000

Signals

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

HUNTONIT EIENDOM AS is registered as a limited company in Vennesla, Agder with organisation number 927730421. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 391,000, divided into 100 shares. The company's stated purpose is: “Utvikling, utbygging, kjøp, salg og utleie av eiendom, samt drift av fast eiendom og alt som herved står i forbindelse, herunder å delta i selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.8m in revenue and NOK 15.2m in operating profit.

Key figures · 2024

Revenue
NOK 16.8m
Operating profit
NOK 15.2m
Equity
NOK 749,000
Est. value
NOK 26.6m

Financial health · 2024

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Not satisfactory
Equity as a share of total capital

Who owns HUNTONIT EIENDOM AS?

BYGGMA EIENDOM AS
HUNTONIT EIENDOM AS
NOK 16.8m rev. · NOK 15.2m profit

HUNTONIT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUNTONIT EIENDOM AS

Who owns HUNTONIT EIENDOM AS?

BYGGMA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HUNTONIT EIENDOM AS?

HUNTONIT EIENDOM AS had revenue of NOK 16.8m in 2024.

Where is HUNTONIT EIENDOM AS based?

HUNTONIT EIENDOM AS has its business address in Vennesla.

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.