BIZTRAC BETA
COMPANY REGISTER PROFILE
936185967 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

FOYN HANDELSEIENDOM AS

Org. no. 936185967 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 36,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.
  • Nylig endring 2026-04-09 Adresseendring registrert 2026-04-09.

FOYN HANDELSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 936185967. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 36,000, divided into 3000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Former names: AFAS 080925-09 AS, OTE LEDIG 2 AS

Who owns FOYN HANDELSEIENDOM AS?

FOYN HANDELSEIENDOM AS

FOYN HANDELSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOYN HANDELSEIENDOM AS

Who owns FOYN HANDELSEIENDOM AS?

OTTERLEI FORVALTNING AS is the largest registered owner, with 100.0%.

Where is FOYN HANDELSEIENDOM AS based?

FOYN HANDELSEIENDOM AS has its business address in Oslo.

Property

Business address c/o Malling & Co Forvaltning AS Dronning Mauds gate 15, 0250 Oslo
Cadastral unit 301-209/430/0/0

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