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

ESTATOR EIENDOM AS

Org. no. 992378948 Limited company (AS) Oslo Incorporated 2008 Active
Revenue 2025 NOK 1.0m
Operating profit NOK 396,000
Equity NOK 7.2m
Incorporated 2008
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ESTATOR EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 992378948. 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 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom og hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 396,000 in operating profit.

Former names: STARTPAKKE 25 AS

Key figures · 2025

Revenue
NOK 1.0m
▲ +2 %
Operating profit
NOK 396,000
▼ −38 %
Equity
NOK 7.2m
▼ −1 %
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
8.41
Very good
Current assets ÷ current liabilities
Profitability
4.2%
Weak
Return on total assets
Solidity
75.5%
Very good
Equity as a share of total capital

Who owns ESTATOR EIENDOM AS?

ESTATOR EIENDOM AS
NOK 1.0m rev. · NOK 396,000 profit

ESTATOR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESTATOR EIENDOM AS

Who owns ESTATOR EIENDOM AS?

ESTATOR AS is the largest registered owner, with 100.0%.

What is the revenue of ESTATOR EIENDOM AS?

ESTATOR EIENDOM AS had revenue of NOK 1.0m in 2025.

Where is ESTATOR EIENDOM AS based?

ESTATOR 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.