BIZTRAC BETA
COMPANY REGISTER PROFILE
837035872 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

FRØYA BUSINESS MANAGEMENT AS

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

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-08.
  • Nylig endring 2026-08-25 Adresseendring registrert 2026-08-25.

FRØYA BUSINESS MANAGEMENT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 837035872. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å yte tjenester knyttet til administrasjon og forretningsførsel, herunder regnskapsførsel og rådgivning, samt hva naturlig følger med dette.”.

Who owns FRØYA BUSINESS MANAGEMENT AS?

No shareholders are registered for FRØYA BUSINESS MANAGEMENT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FRØYA BUSINESS MANAGEMENT AS

Who is the general manager of FRØYA BUSINESS MANAGEMENT AS?

Ove Rød Henriksen is registered as general manager of FRØYA BUSINESS MANAGEMENT AS.

Where is FRØYA BUSINESS MANAGEMENT AS based?

FRØYA BUSINESS MANAGEMENT AS has its business address in Trondheim.

Property

Business address Dyre Halses gate 1A, 7042 Trondheim
Cadastral unit 5001-410/665/0/0

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