BIZTRAC BETA
Rental and operating of own or leased real estate

SANNES EIENDOM AS

Org. no. 915718442 Limited company (AS) Haugesund Incorporated 1964 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 3.7m
Equity NOK 20.9m
Incorporated 1964
Share capital NOK 180,000

Signals

1 flags
  • Nylig endring 2026-07-10 Aksjekapital registrert 2026-07-10.

SANNES EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 915718442. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1964. Registered share capital is NOK 180,000, divided into 900 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt drive finansieringsvirksomhet og annen virksomhet som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
Operating profit
NOK 3.7m
Equity
NOK 20.9m
Est. value
NOK 17.5m

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.4%
Good
Equity as a share of total capital

Who owns SANNES EIENDOM AS?

AUDHILD LILLIAN SANNES
SANNES EIENDOM AS
NOK 7.8m rev. · NOK 3.7m profit

SANNES EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANNES EIENDOM AS

Who owns SANNES EIENDOM AS?

AUDHILD LILLIAN SANNES is the largest registered owner, with 25.0%.

What is the revenue of SANNES EIENDOM AS?

SANNES EIENDOM AS had revenue of NOK 7.8m in 2025.

Who is the general manager of SANNES EIENDOM AS?

Kjerstin Sannes is registered as general manager of SANNES EIENDOM AS.

Where is SANNES EIENDOM AS based?

SANNES EIENDOM AS has its business address in Haugesund.

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.