BIZTRAC BETA
Rental and operating of own or leased real estate

LYSRUD BIL OG EIENDOM AS

Org. no. 991383743 Limited company (AS) Ringsaker Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 4.1m
Equity NOK 21.8m
Incorporated 2007
Share capital NOK 1.0m

LYSRUD BIL OG EIENDOM AS is registered as a limited company in Ringsaker, Innlandet with organisation number 991383743. 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 1.0m, divided into 1040 shares. The company's stated purpose is: “Investering i fast eiendom for utvikling, salg og utleie, samt transport av gods og det som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 4.1m
Equity
NOK 21.8m
Est. value
NOK 25.6m

Financial health · 2025

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

Who owns LYSRUD BIL OG EIENDOM AS?

NILS ANDERS LYSRUD
LYSRUD BIL OG EIENDOM AS
NOK 6.9m rev. · NOK 4.1m profit

LYSRUD BIL OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSRUD BIL OG EIENDOM AS

Who owns LYSRUD BIL OG EIENDOM AS?

NILS ANDERS LYSRUD is the largest registered owner, with 100.0%.

What is the revenue of LYSRUD BIL OG EIENDOM AS?

LYSRUD BIL OG EIENDOM AS had revenue of NOK 6.9m in 2025.

Who is the general manager of LYSRUD BIL OG EIENDOM AS?

Nils Anders Lysrud is registered as general manager of LYSRUD BIL OG EIENDOM AS.

Where is LYSRUD BIL OG EIENDOM AS based?

LYSRUD BIL OG EIENDOM AS has its business address in Brumunddal.

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.