BIZTRAC BETA
Rental and operating of own or leased real estate

LOGISTEA HOLSNESET AS

Org. no. 987869399 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 2.9m
Equity NOK 16.4m
Incorporated 2005
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.

LOGISTEA HOLSNESET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 987869399. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 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 5.1m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 2.9m
Equity
NOK 16.4m
Est. value
NOK 18.1m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
61.5%
Very good
Equity as a share of total capital

Who owns LOGISTEA HOLSNESET AS?

LOGISTEA PROPERTIES IV NORWAY AS
LOGISTEA HOLSNESET AS
NOK 5.1m rev. · NOK 2.9m profit

LOGISTEA HOLSNESET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGISTEA HOLSNESET AS

Who owns LOGISTEA HOLSNESET AS?

LOGISTEA PROPERTIES IV NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of LOGISTEA HOLSNESET AS?

LOGISTEA HOLSNESET AS had revenue of NOK 5.1m in 2025.

Where is LOGISTEA HOLSNESET AS based?

LOGISTEA HOLSNESET 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.