BIZTRAC BETA
Freight coastal transport

FRØY TOPCO AS

Org. no. 930938564 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −1.9m
Equity NOK 5.0bn
Incorporated 2023
Share capital NOK 1.0m

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-20 Adresseendring registrert 2026-03-20.

FRØY TOPCO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930938564. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 5003782266 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −1.9m
Equity
NOK 5.0bn
Est. value
NOK 5.3bn

Financial health · 2024

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

Who owns FRØY TOPCO AS?

WSIP IV FALCON JV 2 S.À R.L.
FRØY TOPCO AS
· NOK −1.9m profit

FRØY TOPCO AS has 6 registered shareholders:

All shareholders and roles →

Which companies does FRØY TOPCO AS own?

FRØY TOPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRØY TOPCO AS

Who owns FRØY TOPCO AS?

WSIP IV FALCON JV 2 S.À R.L. is the largest registered owner, with 96.3%.

Who is the general manager of FRØY TOPCO AS?

Tonje Eskeland Foss is registered as general manager of FRØY TOPCO AS.

Where is FRØY TOPCO AS based?

FRØY TOPCO 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.