BIZTRAC BETA
Development of building projects

SVEISTRUP EIENDOM AS

Org. no. 989271520 Limited company (AS) Aurskog-Høland Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK −197,000
Equity NOK 12.4m
Incorporated 2005
Share capital NOK 200,000

Signals

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

SVEISTRUP EIENDOM AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 989271520. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 120,000 in revenue and NOK −197,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK −197,000
Equity
NOK 12.4m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns SVEISTRUP EIENDOM AS?

STIAN SVEISTRUP HOLDING AS
SVEISTRUP EIENDOM AS
NOK 120,000 rev. · NOK −197,000 profit

SVEISTRUP EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVEISTRUP EIENDOM AS

Who owns SVEISTRUP EIENDOM AS?

STIAN SVEISTRUP HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of SVEISTRUP EIENDOM AS?

SVEISTRUP EIENDOM AS had revenue of NOK 120,000 in 2024.

Who is the general manager of SVEISTRUP EIENDOM AS?

Jan Sveistrup is registered as general manager of SVEISTRUP EIENDOM AS.

Where is SVEISTRUP EIENDOM AS based?

SVEISTRUP EIENDOM AS has its business address in Aurskog.

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.