BIZTRAC BETA
Construction of residential and non-residential buildings

BJØRN VIDAR JØRGENSEN AS

Org. no. 996669041 Limited company (AS) Marker Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 18,000
Equity NOK 222,000
Incorporated 2011
Share capital NOK 700,000

BJØRN VIDAR JØRGENSEN AS is registered as a limited company in Marker, Østfold with organisation number 996669041. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 700,000, divided into 100 shares. The company's stated purpose is: “Maskinentrepenør og gravevirksomhet innen grunnarbeid, samt tømrer og byggevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 18,000
Equity
NOK 222,000
Est. value
NOK 156,000

Financial health · 2025

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

Who owns BJØRN VIDAR JØRGENSEN AS?

BJØRN VIDAR JØRGENSEN
BJØRN VIDAR JØRGENSEN AS
NOK 3.7m rev. · NOK 18,000 profit

BJØRN VIDAR JØRGENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRN VIDAR JØRGENSEN AS

Who owns BJØRN VIDAR JØRGENSEN AS?

BJØRN VIDAR JØRGENSEN is the largest registered owner, with 100.0%.

What is the revenue of BJØRN VIDAR JØRGENSEN AS?

BJØRN VIDAR JØRGENSEN AS had revenue of NOK 3.7m in 2025.

Who is the general manager of BJØRN VIDAR JØRGENSEN AS?

Bjørn Vidar Jørgensen is registered as general manager of BJØRN VIDAR JØRGENSEN AS.

Where is BJØRN VIDAR JØRGENSEN AS based?

BJØRN VIDAR JØRGENSEN AS has its business address in Ørje.

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.