BIZTRAC BETA
Accounting and bookkeeping

TROMØY REGNSKAPS-SERVICE AS

Org. no. 821373832 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 78,000
Equity NOK 157,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-08-06 Adresseendring registrert 2026-08-06.

TROMØY REGNSKAPS-SERVICE AS is registered as a limited company in Arendal, Agder with organisation number 821373832. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive regnskapstjenester og dertil hørende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 78,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 78,000
Equity
NOK 157,000
Est. value
NOK 425,000

Financial health · 2024

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

Who owns TROMØY REGNSKAPS-SERVICE AS?

CECILIE ELMENHORST
TROMØY REGNSKAPS-SERVICE AS
NOK 1.9m rev. · NOK 78,000 profit

TROMØY REGNSKAPS-SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROMØY REGNSKAPS-SERVICE AS

Who owns TROMØY REGNSKAPS-SERVICE AS?

CECILIE ELMENHORST is the largest registered owner, with 50.0%.

What is the revenue of TROMØY REGNSKAPS-SERVICE AS?

TROMØY REGNSKAPS-SERVICE AS had revenue of NOK 1.9m in 2024.

Who is the general manager of TROMØY REGNSKAPS-SERVICE AS?

Cecilie Elmenhorst is registered as general manager of TROMØY REGNSKAPS-SERVICE AS.

Where is TROMØY REGNSKAPS-SERVICE AS based?

TROMØY REGNSKAPS-SERVICE AS has its business address in Færvik.

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.