BIZTRAC BETA
Rental and operating of own or leased real estate

LOGISTEA HAVØYSUND AS

Org. no. 923013342 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.7m
Equity NOK 748,000
Incorporated 2018
Share capital NOK 748,000

Signals

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

LOGISTEA HAVØYSUND AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923013342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 748,000, divided into 54988 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 1.7m
Equity
NOK 748,000
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns LOGISTEA HAVØYSUND AS?

LOGISTEA PROPERTIES II NORD-NORGE AS
LOGISTEA HAVØYSUND AS
NOK 3.0m rev. · NOK 1.7m profit

LOGISTEA HAVØYSUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGISTEA HAVØYSUND AS

Who owns LOGISTEA HAVØYSUND AS?

LOGISTEA PROPERTIES II NORD-NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of LOGISTEA HAVØYSUND AS?

LOGISTEA HAVØYSUND AS had revenue of NOK 3.0m in 2025.

Where is LOGISTEA HAVØYSUND AS based?

LOGISTEA HAVØYSUND AS has its business address in Trondheim.

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.