BIZTRAC BETA
Development of building projects

SEIDEL INVEST AS

Org. no. 988425281 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −514,000
Equity NOK 7.8m
Incorporated 2005
Share capital NOK 211,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−514k kr).
  • Nylig endring 2026-04-20 Adresseendring registrert 2026-04-20.

SEIDEL INVEST AS is registered as a limited company in Frogn, Akershus with organisation number 988425281. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 211,000, divided into 1 shares. The company's stated purpose is: “Handel med finansielle instrumenter, å eie og forvalte fast eiendom og andre ressurser og annen virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper, samt investeringer i verdipapirer og andre formuesobjekter.”.

Key figures · 2024

Operating profit
NOK −514,000
Equity
NOK 7.8m
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns SEIDEL INVEST AS?

ESPEN SEIDEL
SEIDEL INVEST AS
· NOK −514,000 profit

SEIDEL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEIDEL INVEST AS own?

SEIDEL INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SEIDEL INVEST AS

Who owns SEIDEL INVEST AS?

ESPEN SEIDEL is the largest registered owner, with 100.0%.

Who is the general manager of SEIDEL INVEST AS?

Espen Seidel is registered as general manager of SEIDEL INVEST AS.

Where is SEIDEL INVEST AS based?

SEIDEL INVEST AS has its business address in Drøbak.

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.