BIZTRAC BETA
Rental and operating of own or leased real estate

BREVIK VERFT AS

Org. no. 922717907 Limited company (AS) Porsgrunn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 13.9m
Operating profit NOK 2.9m
Equity NOK 30.5m
Incorporated 2019
Share capital NOK 298,000

Signals

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

BREVIK VERFT AS is registered as a limited company in Porsgrunn, Telemark with organisation number 922717907. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 298,000, divided into 3500 shares. The company's stated purpose is: “Eie og investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.9m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 13.9m
Operating profit
NOK 2.9m
Equity
NOK 30.5m
Est. value
NOK 25.8m

Financial health · 2024

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns BREVIK VERFT AS?

TROSVIK GROUP AS
BREVIK VERFT AS
NOK 13.9m rev. · NOK 2.9m profit

BREVIK VERFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREVIK VERFT AS

Who owns BREVIK VERFT AS?

TROSVIK GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of BREVIK VERFT AS?

BREVIK VERFT AS had revenue of NOK 13.9m in 2024.

Who is the general manager of BREVIK VERFT AS?

Jan Brønsten is registered as general manager of BREVIK VERFT AS.

Where is BREVIK VERFT AS based?

BREVIK VERFT AS has its business address in Brevik.

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.