BIZTRAC BETA
Development of building projects

TROSVIK EIENDOM AS

Org. no. 825511962 Limited company (AS) Porsgrunn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.1m
Equity NOK 373,000
Incorporated 2020
Share capital NOK 100,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-05 Aksjekapital registrert 2026-06-05.

TROSVIK EIENDOM AS is registered as a limited company in Porsgrunn, Telemark with organisation number 825511962. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 70000 shares. The company's stated purpose is: “Kjøpe, selge og utvikle eiendom og alt som her tilhører med tjenester samt å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.1m
Equity
NOK 373,000
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
7.72
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns TROSVIK EIENDOM AS?

TROSVIK GROUP AS
TROSVIK EIENDOM AS
NOK 2.6m rev. · NOK 1.1m profit

TROSVIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROSVIK EIENDOM AS

Who owns TROSVIK EIENDOM AS?

TROSVIK GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of TROSVIK EIENDOM AS?

TROSVIK EIENDOM AS had revenue of NOK 2.6m in 2025.

Where is TROSVIK EIENDOM AS based?

TROSVIK EIENDOM AS has its business address in Brevik.

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.