BIZTRAC BETA
Rental and operating of own or leased real estate

TRENDY EIENDOM AS

Org. no. 917440816 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 4.7m
Equity NOK 17.1m
Incorporated 2016
Share capital NOK 451,000

TRENDY EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 917440816. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 451,000, divided into 1000 shares. The company's stated purpose is: “Å foreta investeringer i fast eiendom, herunder kjøp, salg, utleie, drift, forvaltning m.v., samt å foreta investeringer i selskaper med samme formål. I tillegg kommer all annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 4.7m in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 4.7m
Equity
NOK 17.1m
Est. value
NOK 20.7m

Financial health · 2024

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.9%
Good
Equity as a share of total capital

Who owns TRENDY EIENDOM AS?

TRENDY NÆRINGSEIENDOMMER AS
TRENDY EIENDOM AS
NOK 5.8m rev. · NOK 4.7m profit

TRENDY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRENDY EIENDOM AS own?

TRENDY EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRENDY EIENDOM AS

Who owns TRENDY EIENDOM AS?

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

What is the revenue of TRENDY EIENDOM AS?

TRENDY EIENDOM AS had revenue of NOK 5.8m in 2024.

Where is TRENDY EIENDOM AS based?

TRENDY EIENDOM 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.