BIZTRAC BETA
Repair and maintenance of military fighting vehicles, ships, boats, air and spacecraft

RYGGE EIENDOM AS

Org. no. 920633412 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.1m
Equity NOK 32.9m
Incorporated 2018
Share capital NOK 6.0m

RYGGE EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920633412. The business is classified under repair and maintenance of military fighting vehicles, ships, boats, air and spacecraft (NACE 33.180). The company was incorporated in 2018. Registered share capital is NOK 6.0m, divided into 10000 shares. The company's stated purpose is: “Eie og utvikle fast eiendom, herunder all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.1m
Equity
NOK 32.9m
Est. value
NOK 20.8m

Financial health · 2024

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

Who owns RYGGE EIENDOM AS?

KONGSBERG AVIATION MAINTENANCE SERVICES AS
RYGGE EIENDOM AS
NOK 2.2m rev. · NOK 1.1m profit

RYGGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYGGE EIENDOM AS

Who owns RYGGE EIENDOM AS?

KONGSBERG AVIATION MAINTENANCE SERVICES AS is the largest registered owner, with 100.0%.

What is the revenue of RYGGE EIENDOM AS?

RYGGE EIENDOM AS had revenue of NOK 2.2m in 2024.

Who is the general manager of RYGGE EIENDOM AS?

Andre Jægtvik is registered as general manager of RYGGE EIENDOM AS.

Where is RYGGE EIENDOM AS based?

RYGGE EIENDOM AS has its business address in Kjeller.

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.