BIZTRAC BETA
COMPANY REGISTER PROFILE
951632295 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

NORSJØ EIENDOM AS

Org. no. 951632295 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK 14,000
Equity NOK 66,000
Incorporated 1989
Share capital NOK 30,000

NORSJØ EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 951632295. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1989. Registered share capital is NOK 30,000, divided into 2050 shares. The company's stated purpose is: “Forestå kjøp og salg av fast eiendom og verdipapirer, oppføring av bygg og anlegg, samt utleie av løsøre og fast eiendom og lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK 14,000
Equity
NOK 66,000
Est. value
NOK 86,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORSJØ EIENDOM AS?

NILS HINDRUM
NORSJØ EIENDOM AS
NOK 32,000 rev. · NOK 14,000 profit

NORSJØ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSJØ EIENDOM AS

Who owns NORSJØ EIENDOM AS?

NILS HINDRUM is the largest registered owner, with 100.0%.

What is the revenue of NORSJØ EIENDOM AS?

NORSJØ EIENDOM AS had revenue of NOK 32,000 in 2024.

Who is the general manager of NORSJØ EIENDOM AS?

Nils Hindrum is registered as general manager of NORSJØ EIENDOM AS.

Where is NORSJØ EIENDOM AS based?

NORSJØ 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.