BIZTRAC BETA
COMPANY REGISTER PROFILE
937882475 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Activities of adventure companies

SOLSKINNSMUREREN JAKT- OG FISKECAMP AS

Org. no. 937882475 Limited company (AS) Ås Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 100,000

Signals

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

SOLSKINNSMUREREN JAKT- OG FISKECAMP AS is registered as a limited company in Ås, Akershus with organisation number 937882475. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2026. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å drive salg av reiser og opplevelser samt kjøp, salg, utleie og drift av fast eiendom, samt all annen virksomhet som står i forbindelse med dette.”.

Who owns SOLSKINNSMUREREN JAKT- OG FISKECAMP AS?

No shareholders are registered for SOLSKINNSMUREREN JAKT- OG FISKECAMP AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Group structure

SOLSKINNSMUREREN JAKT- OG FISKECAMP AS er morselskap for 1 datterselskap:

Frequently asked questions about SOLSKINNSMUREREN JAKT- OG FISKECAMP AS

Where is SOLSKINNSMUREREN JAKT- OG FISKECAMP AS based?

SOLSKINNSMUREREN JAKT- OG FISKECAMP AS has its business address in Ski.

Property

Business address Gamle Kongevei 16, 1423 Ski
Cadastral unit 3218-106/11/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

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