BIZTRAC BETA
COMPANY REGISTER PROFILE
936186165 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Web search portal activities

GURU FINANS AS

Org. no. 936186165 Limited company (AS) Skien Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Employees 5
Share capital NOK 508,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-08-27 Adresseendring registrert 2026-08-27.

GURU FINANS AS is registered as a limited company in Skien, Telemark with organisation number 936186165. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 508,000, divided into 462041 shares. The company's stated purpose is: “Formidling og rådgivning av husholdningenes økonomiske valgmuligheter, samt drift og utvikling av egne og andre selskapers digitale løsninger. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltakelse i andre selskaper med lignende virksomhet.”.

Who owns GURU FINANS AS?

GURU FINANS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GURU FINANS AS

Who owns GURU FINANS AS?

BAKKEBO AS is the largest registered owner, with 63.6%.

Who is the general manager of GURU FINANS AS?

Ben Roger Elvenes is registered as general manager of GURU FINANS AS.

Where is GURU FINANS AS based?

GURU FINANS AS has its business address in Skien.

Property

Business address Faråsen 33, 3728 Skien
Cadastral unit 4003-216/83/0/0
Building Enebolig · 1 unit

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