BIZTRAC BETA
Masonry and bricklaying activities

BJØRN ERIK LØVLIEN AS

Org. no. 981666941 Limited company (AS) Lillestrøm Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 114,000
Equity NOK 2.1m
Incorporated 2000
Share capital NOK 100,000

BJØRN ERIK LØVLIEN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 981666941. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Murerfirma.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 114,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 114,000
Equity
NOK 2.1m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns BJØRN ERIK LØVLIEN AS?

BJØRN ERIK LØVLIEN
BJØRN ERIK LØVLIEN AS
NOK 3.0m rev. · NOK 114,000 profit

BJØRN ERIK LØVLIEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRN ERIK LØVLIEN AS own?

BJØRN ERIK LØVLIEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRN ERIK LØVLIEN AS

Who owns BJØRN ERIK LØVLIEN AS?

BJØRN ERIK LØVLIEN is the largest registered owner, with 100.0%.

What is the revenue of BJØRN ERIK LØVLIEN AS?

BJØRN ERIK LØVLIEN AS had revenue of NOK 3.0m in 2024.

Who is the general manager of BJØRN ERIK LØVLIEN AS?

Bjørn Erik Løvlien is registered as general manager of BJØRN ERIK LØVLIEN AS.

Where is BJØRN ERIK LØVLIEN AS based?

BJØRN ERIK LØVLIEN AS has its business address in Lillestrøm.

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.