BIZTRAC BETA
Rental and operating of own or leased real estate

NÆSS EIENDOMSSELSKAP AS

Org. no. 993289310 Limited company (AS) Ullensaker Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 733,000
Operating profit NOK 526,000
Equity NOK 7.8m
Incorporated 2008
Share capital NOK 3.7m

NÆSS EIENDOMSSELSKAP AS is registered as a limited company in Ullensaker, Akershus with organisation number 993289310. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 3.7m, divided into 100 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt virksomhet som måtte stå i forbindelse med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 733,000 in revenue and NOK 526,000 in operating profit.

Key figures · 2024

Revenue
NOK 733,000
Operating profit
NOK 526,000
Equity
NOK 7.8m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns NÆSS EIENDOMSSELSKAP AS?

MME INVEST AS
NÆSS EIENDOMSSELSKAP AS
NOK 733,000 rev. · NOK 526,000 profit

NÆSS EIENDOMSSELSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NÆSS EIENDOMSSELSKAP AS

Who owns NÆSS EIENDOMSSELSKAP AS?

MME INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of NÆSS EIENDOMSSELSKAP AS?

NÆSS EIENDOMSSELSKAP AS had revenue of NOK 733,000 in 2024.

Who is the general manager of NÆSS EIENDOMSSELSKAP AS?

Erik Næss is registered as general manager of NÆSS EIENDOMSSELSKAP AS.

Where is NÆSS EIENDOMSSELSKAP AS based?

NÆSS EIENDOMSSELSKAP AS has its business address in Jessheim.

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.