BIZTRAC BETA
Buying and selling of own real estate

SÆTHER EIENDOMSINVEST AS

Org. no. 834081202 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 228,000
Operating profit NOK 170,000
Equity NOK 830,000
Incorporated 2024
Share capital NOK 30,000

SÆTHER EIENDOMSINVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 834081202. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 228,000 in revenue and NOK 170,000 in operating profit.

Key figures · 2025

Revenue
NOK 228,000
Operating profit
NOK 170,000
Equity
NOK 830,000
Est. value
NOK 814,000

Financial health · 2025

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

Who owns SÆTHER EIENDOMSINVEST AS?

HEVEN HOLDING AS
SÆTHER EIENDOMSINVEST AS
NOK 228,000 rev. · NOK 170,000 profit

SÆTHER EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SÆTHER EIENDOMSINVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about SÆTHER EIENDOMSINVEST AS

Who owns SÆTHER EIENDOMSINVEST AS?

HEVEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SÆTHER EIENDOMSINVEST AS?

SÆTHER EIENDOMSINVEST AS had revenue of NOK 228,000 in 2025.

Who is the general manager of SÆTHER EIENDOMSINVEST AS?

Sigurd Sæther is registered as general manager of SÆTHER EIENDOMSINVEST AS.

Where is SÆTHER EIENDOMSINVEST AS based?

SÆTHER EIENDOMSINVEST AS has its business address in Trondheim.

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.