BIZTRAC BETA
Rental and operating of own or leased real estate

SAUDA EIENDOM AS

Org. no. 992685042 Limited company (AS) Sauda Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 361,000
Operating profit NOK 192,000
Equity NOK 269,000
Incorporated 2008
Share capital NOK 100,000

SAUDA EIENDOM AS is registered as a limited company in Sauda, Rogaland with organisation number 992685042. 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 100,000, divided into 100000 shares. The company's stated purpose is: “Drive virksomhet innenfor kjøp, salg, leie og utleie av eiendom og andre eiendeler, samt alt som står i forbindelse med de forannevnte virksomheter, herunder også å eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 361,000 in revenue and NOK 192,000 in operating profit.

Key figures · 2025

Revenue
NOK 361,000
Operating profit
NOK 192,000
Equity
NOK 269,000
Est. value
NOK 660,000

Financial health · 2025

Liquidity
-21.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
103.3%
Very good
Equity as a share of total capital

Who owns SAUDA EIENDOM AS?

FEHIRDE AS
SAUDA EIENDOM AS
NOK 361,000 rev. · NOK 192,000 profit

SAUDA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAUDA EIENDOM AS

Who owns SAUDA EIENDOM AS?

FEHIRDE AS is the largest registered owner, with 34.0%.

What is the revenue of SAUDA EIENDOM AS?

SAUDA EIENDOM AS had revenue of NOK 361,000 in 2025.

Who is the general manager of SAUDA EIENDOM AS?

Odd-Åge Hustveit is registered as general manager of SAUDA EIENDOM AS.

Where is SAUDA EIENDOM AS based?

SAUDA EIENDOM AS has its business address in Sauda.

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.