BIZTRAC BETA
Wholesale of hardware, plumbing and heating equipment and supplies

YTL AS

Org. no. 987945486 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 89,000
Operating profit NOK −29,000
Equity NOK 462,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

YTL AS is registered as a limited company in Bergen, Vestland with organisation number 987945486. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp,salg, montering av produkter til byggebransjen, konsulentvirksomhet, samt alt som står i naturlig sammenheng med dette. Selskapet kan delta i og eller sammen med selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 89,000 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 89,000
Operating profit
NOK −29,000
Equity
NOK 462,000
Est. value
NOK 366,000

Financial health · 2024

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

Who owns YTL AS?

YNGVE LANGELAND
YTL AS
NOK 89,000 rev. · NOK −29,000 profit

YTL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about YTL AS

Who owns YTL AS?

YNGVE LANGELAND is the largest registered owner, with 50.0%.

What is the revenue of YTL AS?

YTL AS had revenue of NOK 89,000 in 2025.

Who is the general manager of YTL AS?

Yngve Langeland is registered as general manager of YTL AS.

Where is YTL AS based?

YTL AS has its business address in Søreidgrend.

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.