BIZTRAC BETA
Construction of residential and non-residential buildings

GYLYS AS

Org. no. 997877233 Limited company (AS) Ringerike Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 33,000
Equity NOK −383,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−383k kr).

GYLYS AS is registered as a limited company in Ringerike, Buskerud with organisation number 997877233. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive med prosjektering, bygging og oppussing av bygninger samt all annen virksomhet forbundet med foranstående, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 33,000
Equity
NOK −383,000
Est. value
NOK 217,000

Financial health · 2025

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

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

Who owns GYLYS AS?

DARIJUS GYLYS
GYLYS AS
NOK 1.2m rev. · NOK 33,000 profit

GYLYS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYLYS AS

Who owns GYLYS AS?

DARIJUS GYLYS is the largest registered owner, with 100.0%.

What is the revenue of GYLYS AS?

GYLYS AS had revenue of NOK 1.2m in 2025.

Who is the general manager of GYLYS AS?

Darijus Gylys is registered as general manager of GYLYS AS.

Where is GYLYS AS based?

GYLYS AS has its business address in Hallingby.

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.