BIZTRAC BETA
Rental and operating of own or leased real estate

SANDSØY FORT AS

Org. no. 985148910 Limited company (AS) Harstad Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 23,000
Operating profit NOK −63,000
Equity NOK 166,000
Incorporated 2002
Share capital NOK 91,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−63k kr).

SANDSØY FORT AS is registered as a limited company in Harstad, Troms with organisation number 985148910. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 91,000, divided into 250 shares. The company's stated purpose is: “Kurs og selskapsarrangement, kjøp og salg av eiendom, eiendomsutvikling, kjøp og salg av sport- og fritidsartikler, friluft og dykkeaktiviteter, historisk ivaretagelse av Sandsøy Fort samt enhver virksomhet som står i forbindelse med disse formålene.”. The most recent filed accounts, for the 2024 financial year, show NOK 23,000 in revenue and NOK −63,000 in operating profit.

Key figures · 2024

Revenue
NOK 23,000
Operating profit
NOK −63,000
Equity
NOK 166,000
Est. value
NOK 124,000

Financial health · 2024

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

Who owns SANDSØY FORT AS?

BJARKØY HOLDING AS
SANDSØY FORT AS
NOK 23,000 rev. · NOK −63,000 profit

SANDSØY FORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDSØY FORT AS

Who owns SANDSØY FORT AS?

BJARKØY HOLDING AS is the largest registered owner, with 97.3%.

What is the revenue of SANDSØY FORT AS?

SANDSØY FORT AS had revenue of NOK 23,000 in 2024.

Where is SANDSØY FORT AS based?

SANDSØY FORT AS has its business address in Sandsøy.

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.