biztrac. BETA
COMPANY REGISTER PROFILE
923398333 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

ELSMARK EIENDOM AS

Org. no. 923398333 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 262,000
Operating profit NOK 234,000
Equity NOK 136,000
Incorporated 2019
Share capital NOK 30,000

ELSMARK EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 923398333. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av eiendommer samt utleie av hus og leiligheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 262,000 in revenue and NOK 234,000 in operating profit.

Former names: GERE & FREKE EIENDOM AS

Key figures · 2025

Revenue
NOK 262,000
▲ +7 %
Operating profit
NOK 234,000
▲ +40 %
Equity
NOK 136,000
▲ +36 %
Est. value
NOK 450,000

Financial health · 2025

Liquidity
-3.90
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
3.9%
Weak
Equity as a share of total capital

Who owns ELSMARK EIENDOM AS?

ELSMARK EIENDOM AS
NOK 262,000 rev. · NOK 234,000 profit

ELSMARK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELSMARK EIENDOM AS

Who owns ELSMARK EIENDOM AS?

ELSMARK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of ELSMARK EIENDOM AS?

ELSMARK EIENDOM AS had revenue of NOK 262,000 in 2025.

Who is the general manager of ELSMARK EIENDOM AS?

Rune Elsmark is registered as general manager of ELSMARK EIENDOM AS.

Where is ELSMARK EIENDOM AS based?

ELSMARK EIENDOM AS has its business address in Oslo.

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.