BIZTRAC BETA
Construction of residential and non-residential buildings

VYRKE BYGG AS

Org. no. 935554462 Limited company (AS) Fredrikstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 882,000
Operating profit NOK −35,000
Equity NOK −15,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

VYRKE BYGG AS is registered as a limited company in Fredrikstad, Østfold with organisation number 935554462. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 882,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 882,000
Operating profit
NOK −35,000
Equity
NOK −15,000

Financial health · 2025

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

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

Who owns VYRKE BYGG AS?

JAN ERIK BÅRLI
VYRKE BYGG AS
NOK 882,000 rev. · NOK −35,000 profit

VYRKE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VYRKE BYGG AS

Who owns VYRKE BYGG AS?

JAN ERIK BÅRLI is the largest registered owner, with 50.0%.

What is the revenue of VYRKE BYGG AS?

VYRKE BYGG AS had revenue of NOK 882,000 in 2025.

Where is VYRKE BYGG AS based?

VYRKE BYGG AS has its business address in Torp.

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.