BIZTRAC BETA
Service activities incidental to water transportation

FÆRDER MARINA AS

Org. no. 920228895 Limited company (AS) Færder Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 170,000
Equity NOK 192,000
Incorporated 2017
Employees 10
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FÆRDER MARINA AS is registered as a limited company in Færder, Vestfold with organisation number 920228895. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Marinadrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 170,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 170,000
Equity
NOK 192,000
Est. value
NOK 684,000

Financial health · 2024

Liquidity
-1.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
199.3%
Very good
Equity as a share of total capital

Who owns FÆRDER MARINA AS?

LABEL AS
FÆRDER MARINA AS
NOK 5.3m rev. · NOK 170,000 profit

FÆRDER MARINA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FÆRDER MARINA AS

Who owns FÆRDER MARINA AS?

LABEL AS is the largest registered owner, with 100.0%.

What is the revenue of FÆRDER MARINA AS?

FÆRDER MARINA AS had revenue of NOK 5.3m in 2024.

Who is the general manager of FÆRDER MARINA AS?

Lasse Brinck Løvstad is registered as general manager of FÆRDER MARINA AS.

Where is FÆRDER MARINA AS based?

FÆRDER MARINA AS has its business address in Tjøme.

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.