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

LIVIDA HOLDING AS

Org. no. 935378427 Limited company (AS) Holmestrand Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

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

LIVIDA HOLDING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 935378427. 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 LIVIDA HOLDING AS?

LIVIDA HOLDING AS

LIVIDA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIVIDA HOLDING AS own?

LIVIDA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIVIDA HOLDING AS

Who owns LIVIDA HOLDING AS?

VIDAR ESPEGARD is the largest registered owner, with 100.0%.

Who is the general manager of LIVIDA HOLDING AS?

Vidar Espegard is registered as general manager of LIVIDA HOLDING AS.

Where is LIVIDA HOLDING AS based?

LIVIDA HOLDING AS has its business address in Sande I Vestfold.

Property

Business address Furulia 29, 3076 Sande I Vestfold
Cadastral unit 3903-414/59/0/0
Building Enebolig · 1 unit

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.