BIZTRAC BETA
Construction of residential and non-residential buildings

SAX EIENDOM AS

Org. no. 998906296 Limited company (AS) Lillehammer Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK −36,000
Equity NOK 451,000
Incorporated 2012
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−36k kr).

SAX EIENDOM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 998906296. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 400,000, divided into 800 shares. The company's stated purpose is: “Utvikling av eiendommer for bygging og salg av boliger, og produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK −36,000
Equity
NOK 451,000
Est. value
NOK 205,000

Financial health · 2025

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

Who owns SAX EIENDOM AS?

ELSE ANTONIE SOLVANG
SAX EIENDOM AS
NOK 32,000 rev. · NOK −36,000 profit

SAX EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAX EIENDOM AS

Who owns SAX EIENDOM AS?

ELSE ANTONIE SOLVANG is the largest registered owner, with 50.0%.

What is the revenue of SAX EIENDOM AS?

SAX EIENDOM AS had revenue of NOK 32,000 in 2024.

Who is the general manager of SAX EIENDOM AS?

Rolf Solvang is registered as general manager of SAX EIENDOM AS.

Where is SAX EIENDOM AS based?

SAX EIENDOM AS has its business address in Lillehammer.

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.