BIZTRAC BETA
Construction of residential and non-residential buildings

ALFABYGG AS

Org. no. 913892941 Limited company (AS) Nittedal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK −157,000
Equity NOK 756,000
Incorporated 2014
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−157k kr).

ALFABYGG AS is registered as a limited company in Nittedal, Akershus with organisation number 913892941. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oppfølging av bygg, rehabilitering, vedlikehold og alt som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK −157,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK −157,000
Equity
NOK 756,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.2%
Good
Equity as a share of total capital

Who owns ALFABYGG AS?

PETRONEL GIANINO RISCANU
ALFABYGG AS
NOK 3.2m rev. · NOK −157,000 profit

ALFABYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALFABYGG AS

Who owns ALFABYGG AS?

PETRONEL GIANINO RISCANU is the largest registered owner, with 100.0%.

What is the revenue of ALFABYGG AS?

ALFABYGG AS had revenue of NOK 3.2m in 2024.

Who is the general manager of ALFABYGG AS?

Petronel Gianino Riscanu is registered as general manager of ALFABYGG AS.

Where is ALFABYGG AS based?

ALFABYGG AS has its business address in Slattum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.