BIZTRAC BETA
COMPANY REGISTER PROFILE
836454472 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

MOLANDSMOEN 25 AS

Org. no. 836454472 Limited company (AS) Fyresdal Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,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.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-20.

MOLANDSMOEN 25 AS is registered as a limited company in Fyresdal, Telemark with organisation number 836454472. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikle næringsareal i Fyresdal kommune.”.

Who owns MOLANDSMOEN 25 AS?

MOLANDSMOEN 25 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOLANDSMOEN 25 AS

Who owns MOLANDSMOEN 25 AS?

FYRESDAL VEKST AS is the largest registered owner, with 100.0%.

Who is the general manager of MOLANDSMOEN 25 AS?

Olav Veum is registered as general manager of MOLANDSMOEN 25 AS.

Where is MOLANDSMOEN 25 AS based?

MOLANDSMOEN 25 AS has its business address in Fyresdal.

Property

Business address Klokkarhamaren 6, 3870 Fyresdal
Cadastral unit 4032-36/102/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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