BIZTRAC BETA
Rental and operating of own or leased real estate

BENTE LUNDBERG EIENDOM AS

Org. no. 925611417 Limited company (AS) Eidsvoll Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 147,000
Equity NOK 4.0m
Incorporated 2020
Share capital NOK 40,000

BENTE LUNDBERG EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 925611417. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 498 shares. The company's stated purpose is: “Selskapets formål er erverv, forvaltning, utvikling og salg av egne faste eiendommer samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 147,000
Equity
NOK 4.0m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns BENTE LUNDBERG EIENDOM AS?

BENTE LUNDBERG
BENTE LUNDBERG EIENDOM AS
NOK 1.4m rev. · NOK 147,000 profit

BENTE LUNDBERG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BENTE LUNDBERG EIENDOM AS

Who owns BENTE LUNDBERG EIENDOM AS?

BENTE LUNDBERG is the largest registered owner, with 99.4%.

What is the revenue of BENTE LUNDBERG EIENDOM AS?

BENTE LUNDBERG EIENDOM AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BENTE LUNDBERG EIENDOM AS?

Bente Lundberg is registered as general manager of BENTE LUNDBERG EIENDOM AS.

Where is BENTE LUNDBERG EIENDOM AS based?

BENTE LUNDBERG EIENDOM AS has its business address in Dal.

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.