BIZTRAC BETA
Floor and wall covering

BERGEN PARKETTSERVICE AS

Org. no. 980946517 Limited company (AS) Bergen Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 675,000
Equity NOK 4.2m
Incorporated 1999
Share capital NOK 100,000

BERGEN PARKETTSERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 980946517. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Byggtapetserfaget, gulvsliping, gulvlegging og lakkering og aktiviteter som er knyttet opp mot dette, samt utleie av maskiner og salg av produkter vedrørende dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 675,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 675,000
Equity
NOK 4.2m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns BERGEN PARKETTSERVICE AS?

MORTEN BIRKELAND
BERGEN PARKETTSERVICE AS
NOK 4.6m rev. · NOK 675,000 profit

BERGEN PARKETTSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGEN PARKETTSERVICE AS

Who owns BERGEN PARKETTSERVICE AS?

MORTEN BIRKELAND is the largest registered owner, with 50.0%.

What is the revenue of BERGEN PARKETTSERVICE AS?

BERGEN PARKETTSERVICE AS had revenue of NOK 4.6m in 2024.

Who is the general manager of BERGEN PARKETTSERVICE AS?

Morten Birkeland is registered as general manager of BERGEN PARKETTSERVICE AS.

Where is BERGEN PARKETTSERVICE AS based?

BERGEN PARKETTSERVICE AS has its business address in Fana.

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.