BIZTRAC BETA
Other real estate activities on a fee or contract basis

NAUSTBUKTA EIENDOM AS

Org. no. 921407424 Limited company (AS) Nærøysund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 230,000
Operating profit NOK 125,000
Equity NOK 755,000
Incorporated 2018
Share capital NOK 775,000

NAUSTBUKTA EIENDOM AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 921407424. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 775,000, divided into 7750 shares. The company's stated purpose is: “Forvaltning av fast eiendom, løsøre og verdipapirer, samt ved aksjer og parter å delta i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 230,000 in revenue and NOK 125,000 in operating profit.

Key figures · 2024

Revenue
NOK 230,000
Operating profit
NOK 125,000
Equity
NOK 755,000
Est. value
NOK 698,000

Financial health · 2024

Liquidity
11.64
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.5%
Good
Equity as a share of total capital

Who owns NAUSTBUKTA EIENDOM AS?

RODO INVEST AS
NAUSTBUKTA EIENDOM AS
NOK 230,000 rev. · NOK 125,000 profit

NAUSTBUKTA EIENDOM AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about NAUSTBUKTA EIENDOM AS

Who owns NAUSTBUKTA EIENDOM AS?

RODO INVEST AS is the largest registered owner, with 12.9%.

What is the revenue of NAUSTBUKTA EIENDOM AS?

NAUSTBUKTA EIENDOM AS had revenue of NOK 230,000 in 2024.

Who is the general manager of NAUSTBUKTA EIENDOM AS?

Håvard Horn is registered as general manager of NAUSTBUKTA EIENDOM AS.

Where is NAUSTBUKTA EIENDOM AS based?

NAUSTBUKTA EIENDOM AS has its business address in Naustbukta.

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.