BIZTRAC BETA
COMPANY REGISTER PROFILE
935631831 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SAASEN HOLDING AS

Org. no. 935631831 Limited company (AS) Færder Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

SAASEN HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 935631831. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Who owns SAASEN HOLDING AS?

SAASEN HOLDING AS

SAASEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAASEN HOLDING AS own?

SAASEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAASEN HOLDING AS

Who owns SAASEN HOLDING AS?

SIMON AASEN is the largest registered owner, with 100.0%.

Who is the general manager of SAASEN HOLDING AS?

Simon Aasen is registered as general manager of SAASEN HOLDING AS.

Where is SAASEN HOLDING AS based?

SAASEN HOLDING AS has its business address in Nøtterøy.

Property

Business address Søndre Løkkevei 4, 3120 Nøtterøy
Cadastral unit 3911-1/504/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.