BIZTRAC BETA
Construction of residential and non-residential buildings

FAGBYGG AS

Org. no. 827861022 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −515,000
Equity NOK −747,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−747k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−515k kr).

FAGBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 827861022. 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: “Selge tjenester og varer innen forsikring, taksering og byggebransjen og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −515,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −515,000
Equity
NOK −747,000

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-74.8%
Weak
Equity as a share of total capital

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

Who owns FAGBYGG AS?

TSHOLM AS
FAGBYGG AS
NOK 1.5m rev. · NOK −515,000 profit

FAGBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FAGBYGG AS

Who owns FAGBYGG AS?

TSHOLM AS is the largest registered owner, with 100.0%.

What is the revenue of FAGBYGG AS?

FAGBYGG AS had revenue of NOK 1.5m in 2024.

Where is FAGBYGG AS based?

FAGBYGG AS has its business address in Oslo.

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.