BIZTRAC BETA
Rental and operating of own or leased real estate

TROMØY EIENDOM AS

Org. no. 931051407 Limited company (AS) Arendal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −880,000
Equity NOK 1.0m
Incorporated 2023
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−880k kr).

TROMØY EIENDOM AS is registered as a limited company in Arendal, Agder with organisation number 931051407. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 600,000, divided into 200 shares. The company's stated purpose is: “Utvikling og salg av tomter, investering i andre selskap, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −880,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −880,000
Equity
NOK 1.0m
Est. value
NOK 721,000

Financial health · 2025

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

Who owns TROMØY EIENDOM AS?

JAN FRODE STUDSRØD
TROMØY EIENDOM AS
NOK 16,000 rev. · NOK −880,000 profit

TROMØY EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROMØY EIENDOM AS

Who owns TROMØY EIENDOM AS?

JAN FRODE STUDSRØD is the largest registered owner, with 25.0%.

What is the revenue of TROMØY EIENDOM AS?

TROMØY EIENDOM AS had revenue of NOK 16,000 in 2025.

Who is the general manager of TROMØY EIENDOM AS?

John Peder Johnsen is registered as general manager of TROMØY EIENDOM AS.

Where is TROMØY EIENDOM AS based?

TROMØY EIENDOM AS has its business address in Arendal.

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.