BIZTRAC BETA
COMPANY REGISTER PROFILE
937354959 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Joinery installation

DIN RENOVERINGSPARTNER AS

Org. no. 937354959 Limited company (AS) Oslo 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-02-23.

DIN RENOVERINGSPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 937354959. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive håndverkstjenester innen bygg og anlegg, herunder snekkervirksomhet, oppussing, rehabilitering og vedlikehold av bygg, samt annen virksomhet som naturlig faller sammen med dette.”.

Former names: ABBYGG AS

Who owns DIN RENOVERINGSPARTNER AS?

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

Frequently asked questions about DIN RENOVERINGSPARTNER AS

Who is the general manager of DIN RENOVERINGSPARTNER AS?

Behzad Sorodi is registered as general manager of DIN RENOVERINGSPARTNER AS.

Where is DIN RENOVERINGSPARTNER AS based?

DIN RENOVERINGSPARTNER AS has its business address in Oslo.

Property

Business address Grenseveien 107, 0663 Oslo
Cadastral unit 301-130/128/0/0
Building Kontor- og administrasjonsbygning, rådhus · 6 units

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