BIZTRAC BETA
COMPANY REGISTER PROFILE
936531571 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

DROFSSEJ HOLDING AS

Org. no. 936531571 Limited company (AS) Sør-Varanger Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-28.

DROFSSEJ HOLDING AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 936531571. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer, verdipapirer og fast eiendom, samt det som står i naturlig sammenheng med dette.”.

Who owns DROFSSEJ HOLDING AS?

DROFSSEJ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DROFSSEJ HOLDING AS own?

DROFSSEJ HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DROFSSEJ HOLDING AS

Who owns DROFSSEJ HOLDING AS?

JESSFORD GAON SIBAYAN is the largest registered owner, with 100.0%.

Who is the general manager of DROFSSEJ HOLDING AS?

Jessford Gaon Sibayan is registered as general manager of DROFSSEJ HOLDING AS.

Where is DROFSSEJ HOLDING AS based?

DROFSSEJ HOLDING AS has its business address in Kirkenes.

Property

Business address Amtmann Graffs gate 19, 9900 Kirkenes
Cadastral unit 5605-27/400/0/0
Building Tomannsbolig, horisontaldelt · 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.