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

SÆTER EIENDOM AS

Org. no. 979577753 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 4.0m
Equity NOK 30,000
Incorporated 1998
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-26 Adresseendring registrert 2026-06-26.

SÆTER EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 979577753. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Erverv, drift og utvikling av fast eiendom, herunder også ved deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
▲ +13 %
Operating profit
NOK 4.0m
▲ +24 %
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 6.1m

Financial health · 2025

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

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

Who owns SÆTER EIENDOM AS?

SÆTER EIENDOM AS
NOK 5.5m rev. · NOK 4.0m profit

SÆTER EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SÆTER EIENDOM AS

Who owns SÆTER EIENDOM AS?

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

What is the revenue of SÆTER EIENDOM AS?

SÆTER EIENDOM AS had revenue of NOK 5.5m in 2025.

Where is SÆTER EIENDOM AS based?

SÆTER 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.