biztrac. BETA
COMPANY REGISTER PROFILE
923107347 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GEIR ANDERSEN EIENDOM AS

Org. no. 923107347 Limited company (AS) Moskenes Incorporated 2019 Active
Revenue 2025 NOK 367,000
Operating profit NOK 7,000
Equity NOK 899,000
Incorporated 2019
Share capital NOK 30,000

GEIR ANDERSEN EIENDOM AS is registered as a limited company in Moskenes, Nordland with organisation number 923107347. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering og drift av eiendom”. The most recent filed accounts, for the 2025 financial year, show NOK 367,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 367,000
▲ +53 %
Operating profit
NOK 7,000
▲ +109 %
Equity
NOK 899,000
▼ −3 %
Est. value
NOK 749,000

Financial health · 2025

Liquidity
3.90
Very good
Current assets ÷ current liabilities
Profitability
0.2%
Not satisfactory
Return on total assets
Solidity
28.6%
Good
Equity as a share of total capital

Who owns GEIR ANDERSEN EIENDOM AS?

GEIR ANDERSEN EIENDOM AS
NOK 367,000 rev. · NOK 7,000 profit

GEIR ANDERSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEIR ANDERSEN EIENDOM AS

Who owns GEIR ANDERSEN EIENDOM AS?

Geir Andersen is the largest registered owner, with 100.0%.

What is the revenue of GEIR ANDERSEN EIENDOM AS?

GEIR ANDERSEN EIENDOM AS had revenue of NOK 367,000 in 2025.

Who is the general manager of GEIR ANDERSEN EIENDOM AS?

Geir Andersen is registered as general manager of GEIR ANDERSEN EIENDOM AS.

Where is GEIR ANDERSEN EIENDOM AS based?

GEIR ANDERSEN EIENDOM AS has its business address in Reine.

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.