BIZTRAC BETA
COMPANY REGISTER PROFILE
936597157 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Site preparation

GEOENERGI AS

Org. no. 936597157 Limited company (AS) Krødsherad Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Employees 26
Share capital NOK 500,000

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.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-31.

GEOENERGI AS is registered as a limited company in Krødsherad, Buskerud with organisation number 936597157. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2025 and has 26 registered employees. Registered share capital is NOK 500,000, divided into 1000000 shares. The company's stated purpose is: “Entreprenørvirksomhet samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Who owns GEOENERGI AS?

GEOENERGI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEOENERGI AS

Who owns GEOENERGI AS?

BÅSUM BORING AS is the largest registered owner, with 100.0%.

Who is the general manager of GEOENERGI AS?

Nils Hanstad is registered as general manager of GEOENERGI AS.

Where is GEOENERGI AS based?

GEOENERGI AS has its business address in Krøderen.

Property

Business address Slettemoen 24, 3535 Krøderen
Cadastral unit 3318-178/273/0/0
Building Kontor- og administrasjonsbygning, rådhus · 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.