BIZTRAC BETA
Construction of residential and non-residential buildings

AZ BYGG OG FLISLEGGER AS

Org. no. 928538257 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 166,000
Operating profit NOK 7,000
Equity NOK 17,000
Incorporated 2021
Share capital NOK 30,000

AZ BYGG OG FLISLEGGER AS is registered as a limited company in Bærum, Akershus with organisation number 928538257. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggservice og oppussing bad.”. The most recent filed accounts, for the 2024 financial year, show NOK 166,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 166,000
Operating profit
NOK 7,000
Equity
NOK 17,000
Est. value
NOK 32,000

Financial health · 2024

Liquidity
2.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AZ BYGG OG FLISLEGGER AS?

ABEL GOYTOM BERHE
AZ BYGG OG FLISLEGGER AS
NOK 166,000 rev. · NOK 7,000 profit

AZ BYGG OG FLISLEGGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AZ BYGG OG FLISLEGGER AS

Who owns AZ BYGG OG FLISLEGGER AS?

ABEL GOYTOM BERHE is the largest registered owner, with 100.0%.

What is the revenue of AZ BYGG OG FLISLEGGER AS?

AZ BYGG OG FLISLEGGER AS had revenue of NOK 166,000 in 2024.

Who is the general manager of AZ BYGG OG FLISLEGGER AS?

Abel Goytom Berhe is registered as general manager of AZ BYGG OG FLISLEGGER AS.

Where is AZ BYGG OG FLISLEGGER AS based?

AZ BYGG OG FLISLEGGER AS has its business address in Jar.

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.