biztrac. BETA
COMPANY REGISTER PROFILE
926776231 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

LYR AS

Org. no. 926776231 Limited company (AS) Gjerdrum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 169,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nylig endring 2026-08-26 Adresseendring registrert 2026-08-26.

LYR AS is registered as a limited company in Gjerdrum, Akershus with organisation number 926776231. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer, andeler og eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Former names: EMATES AS

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −7,000
▼ −204 %
Equity
NOK 169,000
▲ +141 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
27.3%
Very good
Return on total assets
Solidity
60.5%
Very good
Equity as a share of total capital

Who owns LYR AS?

LYR AS
NOK 0 rev. · NOK −7,000 profit

LYR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYR AS own?

LYR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LYR AS

Who owns LYR AS?

Mats Kobbersletten Jensen is the largest registered owner, with 100.0%.

What is the revenue of LYR AS?

LYR AS had revenue of NOK 0 in 2025.

Where is LYR AS based?

LYR AS has its business address in Gjerdrum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.