BIZTRAC BETA
Logistics service activities

FOR AS

Org. no. 932596695 Limited company (AS) Nærøysund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 378,000
Operating profit NOK −102,000
Equity NOK 35.2m
Incorporated 2023
Share capital NOK 30.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−102k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FOR AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 932596695. The business is classified under logistics service activities (NACE 52.250). The company was incorporated in 2023. Registered share capital is NOK 30.1m, divided into 1768991 shares. The company's stated purpose is: “Investering i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 378,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 378,000
Operating profit
NOK −102,000
Equity
NOK 35.2m
Est. value
NOK 18.1m

Financial health · 2024

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

Who owns FOR AS?

SS-INVEST AS
FOR AS
NOK 378,000 rev. · NOK −102,000 profit

FOR AS has 12 registered shareholders:

All shareholders and roles →

Which companies does FOR AS own?

FOR AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FOR AS

Who owns FOR AS?

SS-INVEST AS is the largest registered owner, with 66.5%.

What is the revenue of FOR AS?

FOR AS had revenue of NOK 378,000 in 2024.

Who is the general manager of FOR AS?

Håvard Lundseng Sandnes is registered as general manager of FOR AS.

Where is FOR AS based?

FOR AS has its business address in Kolvereid.

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.