BIZTRAC BETA
Construction of residential and non-residential buildings

WIEDER BYGG AS

Org. no. 929936213 Limited company (AS) Arendal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 16,000
Equity NOK 40,000
Incorporated 2022
Share capital NOK 30,000

WIEDER BYGG AS is registered as a limited company in Arendal, Agder with organisation number 929936213. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bygge hytter, boliger, forretningsbygg med mere, vedlikehold og reparasjoner på og i eksisterende bygninger. Utvikling av prosjekter. Samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 16,000
Equity
NOK 40,000
Est. value
NOK 53,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

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

Who owns WIEDER BYGG AS?

BRAJAN PIOTR WIEDER
WIEDER BYGG AS
NOK 2.6m rev. · NOK 16,000 profit

WIEDER BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIEDER BYGG AS

Who owns WIEDER BYGG AS?

BRAJAN PIOTR WIEDER is the largest registered owner, with 100.0%.

What is the revenue of WIEDER BYGG AS?

WIEDER BYGG AS had revenue of NOK 2.6m in 2025.

Who is the general manager of WIEDER BYGG AS?

Brajan Piotr Wieder is registered as general manager of WIEDER BYGG AS.

Where is WIEDER BYGG AS based?

WIEDER BYGG AS has its business address in Arendal.

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.