BIZTRAC BETA
Site preparation

BJ MASKIN & MEK AS

Org. no. 924900784 Limited company (AS) Indre Østfold Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 1.4m
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

BJ MASKIN & MEK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 924900784. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet, mekaniske arbeider og reparasjoner, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 1.4m
Equity
NOK 1.6m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns BJ MASKIN & MEK AS?

JOHAN GEORG JAHREN
BJ MASKIN & MEK AS
NOK 3.9m rev. · NOK 1.4m profit

BJ MASKIN & MEK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BJ MASKIN & MEK AS own?

BJ MASKIN & MEK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJ MASKIN & MEK AS

Who owns BJ MASKIN & MEK AS?

JOHAN GEORG JAHREN is the largest registered owner, with 50.0%.

What is the revenue of BJ MASKIN & MEK AS?

BJ MASKIN & MEK AS had revenue of NOK 3.9m in 2024.

Who is the general manager of BJ MASKIN & MEK AS?

Johan Georg Jahren is registered as general manager of BJ MASKIN & MEK AS.

Where is BJ MASKIN & MEK AS based?

BJ MASKIN & MEK AS has its business address in Hærland.

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.