BIZTRAC BETA
Rental and operating of own or leased real estate

LINDERUD NÆRING AS

Org. no. 916265042 Limited company (AS) Lillestrøm Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 781,000
Equity NOK 2.2m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LINDERUD NÆRING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 916265042. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, forvaltning og utleie av fast eiendom, samt derved forbunden virksomhet, herunder å drive handel, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 781,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 781,000
Equity
NOK 2.2m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.9%
Satisfactory
Equity as a share of total capital

Who owns LINDERUD NÆRING AS?

TRENDY NÆRINGSEIENDOMMER AS
LINDERUD NÆRING AS
NOK 1.6m rev. · NOK 781,000 profit

LINDERUD NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINDERUD NÆRING AS

Who owns LINDERUD NÆRING AS?

TRENDY NÆRINGSEIENDOMMER AS is the largest registered owner, with 100.0%.

What is the revenue of LINDERUD NÆRING AS?

LINDERUD NÆRING AS had revenue of NOK 1.6m in 2024.

Where is LINDERUD NÆRING AS based?

LINDERUD NÆRING AS has its business address in Lillestrøm.

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.