biztrac. BETA
COMPANY REGISTER PROFILE
930669369 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BM BYGG AS

Org. no. 930669369 Limited company (AS) Lørenskog Incorporated 2022 Active
Revenue 2025 NOK 3.1m
Operating profit NOK 41,000
Equity NOK 133,000
Incorporated 2022
Employees 5
Share capital NOK 30,000

BM BYGG AS is registered as a limited company in Lørenskog, Akershus with organisation number 930669369. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring og renovering og vedlikehold av bygg (maling, flislegging, snekring mm.). Selskapet skal drive virksomhet som står i naturlig forbindelse med det dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
▲ +2 %
Operating profit
NOK 41,000
▼ −50 %
Equity
NOK 133,000
▲ +15 %
Est. value
NOK 217,000

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
10.7%
Good
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns BM BYGG AS?

BM BYGG AS
NOK 3.1m rev. · NOK 41,000 profit

BM BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BM BYGG AS

Who owns BM BYGG AS?

Besnik Emrula is the largest registered owner, with 100.0%.

What is the revenue of BM BYGG AS?

BM BYGG AS had revenue of NOK 3.1m in 2025.

Who is the general manager of BM BYGG AS?

Besnik Emrula is registered as general manager of BM BYGG AS.

Where is BM BYGG AS based?

BM BYGG AS has its business address in Rasta.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.