BIZTRAC BETA
COMPANY REGISTER PROFILE
837595452 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

STORHOLM HOLDING AS

Org. no. 837595452 Limited company (AS) Lillehammer Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-03-06.

STORHOLM HOLDING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 837595452. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og verdipapirer. Videre kan virksomheten bestå av deltakelse i andre selskap med lignende virksomhet, eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp, salg og drift av fast eiendom.”.

Who owns STORHOLM HOLDING AS?

No shareholders are registered for STORHOLM HOLDING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STORHOLM HOLDING AS

Who is the general manager of STORHOLM HOLDING AS?

Roy Magne Storholm is registered as general manager of STORHOLM HOLDING AS.

Where is STORHOLM HOLDING AS based?

STORHOLM HOLDING AS has its business address in Fåberg.

Property

Business address Baklivegen 636, 2625 Fåberg
Cadastral unit 3405-131/1/0/0
Building Våningshus · 1 unit

5 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.