BIZTRAC BETA
Accounting and bookkeeping

TRIO EIENDOMSSERVICE AS

Org. no. 894520132 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 431,000
Equity NOK 1.1m
Incorporated 2009
Share capital NOK 100,000

TRIO EIENDOMSSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 894520132. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Regnskapsføring, lønnskjøring og husleieinnkreving for borettslag, sameier og andre bedrifter og beslektede virksomheter, samt ved aksjetegning eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 431,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 431,000
Equity
NOK 1.1m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns TRIO EIENDOMSSERVICE AS?

SVEIN LILLEBERG
TRIO EIENDOMSSERVICE AS
NOK 2.5m rev. · NOK 431,000 profit

TRIO EIENDOMSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRIO EIENDOMSSERVICE AS

Who owns TRIO EIENDOMSSERVICE AS?

SVEIN LILLEBERG is the largest registered owner, with 100.0%.

What is the revenue of TRIO EIENDOMSSERVICE AS?

TRIO EIENDOMSSERVICE AS had revenue of NOK 2.5m in 2024.

Who is the general manager of TRIO EIENDOMSSERVICE AS?

Simona Aune is registered as general manager of TRIO EIENDOMSSERVICE AS.

Where is TRIO EIENDOMSSERVICE AS based?

TRIO EIENDOMSSERVICE AS has its business address in Tiller.

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.