BIZTRAC BETA
COMPANY REGISTER PROFILE
991438459 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

LYDER SAGENSGT 19 AS

Org. no. 991438459 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 326,000
Equity NOK −3.5m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,5 mill kr).

LYDER SAGENSGT 19 AS is registered as a limited company in Bergen, Vestland with organisation number 991438459. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og drift av fast eiendom samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 326,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 326,000
Equity
NOK −3.5m
Est. value
NOK 2.5m

Financial health · 2024

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

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

Who owns LYDER SAGENSGT 19 AS?

ROY SKADAL
LYDER SAGENSGT 19 AS
NOK 3.2m rev. · NOK 326,000 profit

LYDER SAGENSGT 19 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYDER SAGENSGT 19 AS

Who owns LYDER SAGENSGT 19 AS?

ROY SKADAL is the largest registered owner, with 100.0%.

What is the revenue of LYDER SAGENSGT 19 AS?

LYDER SAGENSGT 19 AS had revenue of NOK 3.2m in 2024.

Where is LYDER SAGENSGT 19 AS based?

LYDER SAGENSGT 19 AS has its business address in Eidsvåg I Åsane.

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.