BIZTRAC BETA
Rental and operating of own or leased real estate

NITTENTJUE EIENDOM AS

Org. no. 828554972 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 693,000
Operating profit NOK 435,000
Equity NOK 3.7m
Incorporated 2022
Share capital NOK 60,000

NITTENTJUE EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 828554972. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Investere i eiendom for utleie og salg. Selskapet vil også ta del i andre selskaper der dette kan gi et økonomisk og faglig utbytte.”. The most recent filed accounts, for the 2025 financial year, show NOK 693,000 in revenue and NOK 435,000 in operating profit.

Key figures · 2025

Revenue
NOK 693,000
Operating profit
NOK 435,000
Equity
NOK 3.7m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns NITTENTJUE EIENDOM AS?

DØHLEN AS
NITTENTJUE EIENDOM AS
NOK 693,000 rev. · NOK 435,000 profit

NITTENTJUE EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NITTENTJUE EIENDOM AS

Who owns NITTENTJUE EIENDOM AS?

DØHLEN AS is the largest registered owner, with 33.3%.

What is the revenue of NITTENTJUE EIENDOM AS?

NITTENTJUE EIENDOM AS had revenue of NOK 693,000 in 2025.

Who is the general manager of NITTENTJUE EIENDOM AS?

Jens Kristian Stakkerud is registered as general manager of NITTENTJUE EIENDOM AS.

Where is NITTENTJUE EIENDOM AS based?

NITTENTJUE EIENDOM AS has its business address in Sørumsand.

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.