biztrac. BETA
COMPANY REGISTER PROFILE
913307801 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

LØVBERG BYGG OG EIENDOM AS

Org. no. 913307801 Limited company (AS) Gjerdrum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 1.2m
Equity NOK 5.1m
Incorporated 2014
Employees 5
Share capital NOK 100,000

LØVBERG BYGG OG EIENDOM AS is registered as a limited company in Gjerdrum, Akershus with organisation number 913307801. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive snekkertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
▲ +86 %
Operating profit
NOK 1.2m
▲ +60 %
Equity
NOK 5.1m
▲ +17 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
7.25
Very good
Current assets ÷ current liabilities
Profitability
10.6%
Good
Return on total assets
Solidity
41.4%
Very good
Equity as a share of total capital

Who owns LØVBERG BYGG OG EIENDOM AS?

LØVBERG BYGG OG EIENDOM AS
NOK 4.7m rev. · NOK 1.2m profit

LØVBERG BYGG OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVBERG BYGG OG EIENDOM AS

Who owns LØVBERG BYGG OG EIENDOM AS?

LØVBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LØVBERG BYGG OG EIENDOM AS?

LØVBERG BYGG OG EIENDOM AS had revenue of NOK 4.7m in 2025.

Who is the general manager of LØVBERG BYGG OG EIENDOM AS?

Vidar Løvberg is registered as general manager of LØVBERG BYGG OG EIENDOM AS.

Where is LØVBERG BYGG OG EIENDOM AS based?

LØVBERG BYGG OG EIENDOM AS has its business address in Gjerdrum.

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.