BIZTRAC BETA
Service activities incidental to water transportation

FRØY CREW AS

Org. no. 892132402 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −33,000
Equity NOK 12.8m
Incorporated 2007
Employees 382
Share capital NOK 125,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−33k 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-10 Adresseendring registrert 2026-03-10.

FRØY CREW AS is registered as a limited company in Trondheim, Trøndelag with organisation number 892132402. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2007 and has 382 registered employees. Registered share capital is NOK 125,000, divided into 125 shares. The company's stated purpose is: “Konsulentbistand, utleie av arbeidskraft innen maritim- og offshorevirksomhet, forvaltning av fast eiendom, løsøre og verdipapir, samt ved aksjer og parter å delta i andre selskaper og virksomheter.”.

Key figures · 2024

Operating profit
NOK −33,000
Equity
NOK 12.8m
Est. value
NOK 9.7m

Financial health · 2024

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

Who owns FRØY CREW AS?

FRØY AS
FRØY CREW AS
· NOK −33,000 profit

FRØY CREW AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRØY CREW AS own?

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

See the full ownership structure →

Frequently asked questions about FRØY CREW AS

Who owns FRØY CREW AS?

FRØY AS is the largest registered owner, with 100.0%.

Where is FRØY CREW AS based?

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