BIZTRAC BETA
Masonry and bricklaying activities

OSLO MURERNE AS

Org. no. 984775431 Limited company (AS) Enebakk Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −134,000
Equity NOK −325,000
Incorporated 2002
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−325k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−134k kr).

OSLO MURERNE AS is registered as a limited company in Enebakk, Akershus with organisation number 984775431. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Mur og pussarbeid og flisarbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −134,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −134,000
Equity
NOK −325,000

Financial health · 2024

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-68.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OSLO MURERNE AS?

SVEIN-ERIK BÅLERUD
OSLO MURERNE AS
NOK 2.9m rev. · NOK −134,000 profit

OSLO MURERNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO MURERNE AS

Who owns OSLO MURERNE AS?

SVEIN-ERIK BÅLERUD is the largest registered owner, with 100.0%.

What is the revenue of OSLO MURERNE AS?

OSLO MURERNE AS had revenue of NOK 2.9m in 2024.

Who is the general manager of OSLO MURERNE AS?

Svein-Erik Bålerud is registered as general manager of OSLO MURERNE AS.

Where is OSLO MURERNE AS based?

OSLO MURERNE AS has its business address in Ytre Enebakk.

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.