BIZTRAC BETA
Rental and operating of own or leased real estate

LOGISTEA BÅTSFJORD AS

Org. no. 923013059 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 1.6m
Equity NOK 8.8m
Incorporated 2019
Share capital NOK 55,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 BÅTSFJORD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923013059. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 55,000, divided into 2479 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.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 1.6m
Equity
NOK 8.8m
Est. value
NOK 9.6m

Financial health · 2025

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

Who owns LOGISTEA BÅTSFJORD AS?

LOGISTEA PROPERTIES II NORD-NORGE AS
LOGISTEA BÅTSFJORD AS
NOK 3.1m rev. · NOK 1.6m profit

LOGISTEA BÅTSFJORD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGISTEA BÅTSFJORD AS

Who owns LOGISTEA BÅTSFJORD AS?

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

What is the revenue of LOGISTEA BÅTSFJORD AS?

LOGISTEA BÅTSFJORD AS had revenue of NOK 3.1m in 2025.

Where is LOGISTEA BÅTSFJORD AS based?

LOGISTEA BÅTSFJORD 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.