BIZTRAC BETA
Development of building projects

TREVI EIENDOM AS

Org. no. 932366312 Limited company (AS) Lyngdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 500,000
Operating profit NOK 55,000
Equity NOK −115,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−115k kr).

TREVI EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 932366312. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling, forvaltning og utleie av fast eiendom og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet samt øvrige aksjeinvesteringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 500,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 500,000
Operating profit
NOK 55,000
Equity
NOK −115,000
Est. value
NOK 583,000

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TREVI EIENDOM AS?

FJELLBORG HOLDING AS
TREVI EIENDOM AS
NOK 500,000 rev. · NOK 55,000 profit

TREVI EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TREVI EIENDOM AS

Who owns TREVI EIENDOM AS?

FJELLBORG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TREVI EIENDOM AS?

TREVI EIENDOM AS had revenue of NOK 500,000 in 2025.

Where is TREVI EIENDOM AS based?

TREVI EIENDOM AS has its business address in Byremo.

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.