BIZTRAC BETA
COMPANY REGISTER PROFILE
938211124 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Norwegian company

EGMABYGG AS

Org. no. 938211124 Limited company (AS) Nordre Follo 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-06-10.

EGMABYGG AS is registered as a limited company in Nordre Follo, Akershus with organisation number 938211124. The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rehabilitering av bygninger, oppussing, oppfølging av byggearbeider, snekkerarbeid, entreprenør, interiør, anleggsarbeid, anleggsgartnertjenester, grunnarbeider, muring, tømrerarbeider, maling, taktekking, garasje bygging, terrasser installasjon og alt som følger naturlig av denne bransjen. Annen forretningsmessig tjenesteyting ikke nevnt annet sted og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Who owns EGMABYGG AS?

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

Frequently asked questions about EGMABYGG AS

Where is EGMABYGG AS based?

EGMABYGG AS has its business address in Ski.

Property

Business address Kirkeveien 53, 1400 Ski
Cadastral unit 3207-131/25/0/0
Building Enebolig · 1 unit

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.