BIZTRAC BETA
Uoppgitt

SE INVEST OG EIENDOM AS

Org. no. 984825218 Limited company (AS) Kongsberg Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 314,000
Incorporated 2002
Share capital NOK 104,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

SE INVEST OG EIENDOM AS is registered as a limited company in Kongsberg, Buskerud with organisation number 984825218. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2002. Registered share capital is NOK 104,000, divided into 52 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, arbeider innen bygg og anlegg samt deltagelse i andre selskaper, herunder kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 314,000
Est. value
NOK 369,000

Financial health · 2025

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

Who owns SE INVEST OG EIENDOM AS?

SISS ENGELHART
SE INVEST OG EIENDOM AS
NOK 0 rev. · NOK −16,000 profit

SE INVEST OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SE INVEST OG EIENDOM AS

Who owns SE INVEST OG EIENDOM AS?

SISS ENGELHART is the largest registered owner, with 100.0%.

What is the revenue of SE INVEST OG EIENDOM AS?

SE INVEST OG EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of SE INVEST OG EIENDOM AS?

Magne Tangen is registered as general manager of SE INVEST OG EIENDOM AS.

Where is SE INVEST OG EIENDOM AS based?

SE INVEST OG EIENDOM AS has its business address in Kongsberg.

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.