BIZTRAC BETA
Buying and selling of own real estate

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS

Org. no. 935857309 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 28.7m

Signals

3 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-07-20 Aksjekapital registrert 2026-07-20.

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS is registered as a limited company in Oslo, Oslo with organisation number 935857309. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 28.7m, divided into 2865270 shares. The company's stated purpose is: “Å gjøre investering, utvikling, utleie og drift av fast eiendom og annen virksomhet som står i forbindelse med dette, herunder investering i andre selskaper.”.

Who owns SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS?

PECUNIA EIENDOMSPARTNER AS
SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS has 7 registered shareholders:

All shareholders and roles →

Which companies does SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS own?

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS

Who owns SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS?

PECUNIA EIENDOMSPARTNER AS is the largest registered owner, with 54.8%.

Who is the general manager of SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS?

Ulf Øyvind Lund is registered as general manager of SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS.

Where is SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS based?

SEQUOIA PROSJEKT OLAV BRUNBORGS VEI AS has its business address in Oslo.

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.