BIZTRAC BETA
Rental and operating of own or leased real estate

GLEMMEN EIENDOM I AS

Org. no. 994255533 Limited company (AS) Sarpsborg Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 1.7m
Equity NOK 1.9m
Incorporated 2009
Share capital NOK 500,000

GLEMMEN EIENDOM I AS is registered as a limited company in Sarpsborg, Østfold with organisation number 994255533. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og utvikle fast eiendom og virksomhet som har sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 1.7m
Equity
NOK 1.9m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Who owns GLEMMEN EIENDOM I AS?

DAHLE EIENDOM HOLDING AS
GLEMMEN EIENDOM I AS
NOK 3.2m rev. · NOK 1.7m profit

GLEMMEN EIENDOM I AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GLEMMEN EIENDOM I AS er morselskap for 14 datterselskaper:

Frequently asked questions about GLEMMEN EIENDOM I AS

Who owns GLEMMEN EIENDOM I AS?

DAHLE EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GLEMMEN EIENDOM I AS?

GLEMMEN EIENDOM I AS had revenue of NOK 3.2m in 2024.

Who is the general manager of GLEMMEN EIENDOM I AS?

Henrik Walstad is registered as general manager of GLEMMEN EIENDOM I AS.

Where is GLEMMEN EIENDOM I AS based?

GLEMMEN EIENDOM I AS has its business address in Sarpsborg.

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.