BIZTRAC BETA
Freight coastal transport

FAIR WINDS SERVICES AS

Org. no. 918800727 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK −2,000
Equity NOK 14,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

FAIR WINDS SERVICES AS is registered as a limited company in Oslo, Oslo with organisation number 918800727. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Sjøfart og kysttrafikk med gods og undervisning ikke nevnt annet sted.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK −2,000
Equity
NOK 14,000
Est. value
NOK 22,000

Financial health · 2024

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FAIR WINDS SERVICES AS?

MILOT BELAJ
FAIR WINDS SERVICES AS
NOK 32,000 rev. · NOK −2,000 profit

FAIR WINDS SERVICES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAIR WINDS SERVICES AS

Who owns FAIR WINDS SERVICES AS?

MILOT BELAJ is the largest registered owner, with 50.0%.

What is the revenue of FAIR WINDS SERVICES AS?

FAIR WINDS SERVICES AS had revenue of NOK 32,000 in 2024.

Who is the general manager of FAIR WINDS SERVICES AS?

Milot Belaj is registered as general manager of FAIR WINDS SERVICES AS.

Where is FAIR WINDS SERVICES AS based?

FAIR WINDS SERVICES AS has its business address in Oslo.

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.