BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRGVIN FABRIKKER AS

Org. no. 985968934 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 594,000
Operating profit NOK 451,000
Equity NOK 2.9m
Incorporated 2003
Share capital NOK 102,000

BJØRGVIN FABRIKKER AS is registered as a limited company in Bergen, Vestland with organisation number 985968934. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Fabrikkdrift, handel og dermed sammenhengende virksomhet, kjøp og salg av fast eiendom og aksjer, samt deltakelse for øvrig i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 594,000 in revenue and NOK 451,000 in operating profit.

Key figures · 2025

Revenue
NOK 594,000
Operating profit
NOK 451,000
Equity
NOK 2.9m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns BJØRGVIN FABRIKKER AS?

CELINE GABRIELE FALCK
BJØRGVIN FABRIKKER AS
NOK 594,000 rev. · NOK 451,000 profit

BJØRGVIN FABRIKKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRGVIN FABRIKKER AS

Who owns BJØRGVIN FABRIKKER AS?

CELINE GABRIELE FALCK is the largest registered owner, with 78.4%.

What is the revenue of BJØRGVIN FABRIKKER AS?

BJØRGVIN FABRIKKER AS had revenue of NOK 594,000 in 2025.

Who is the general manager of BJØRGVIN FABRIKKER AS?

Petter Georg Falck is registered as general manager of BJØRGVIN FABRIKKER AS.

Where is BJØRGVIN FABRIKKER AS based?

BJØRGVIN FABRIKKER AS has its business address in Bergen.

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.