BIZTRAC BETA
Buying and selling of own real estate

TJØLLINGVEIEN 520 AS

Org. no. 829578352 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 189,000
Operating profit NOK 121,000
Equity NOK −605,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−605k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TJØLLINGVEIEN 520 AS is registered as a limited company in Larvik, Vestfold with organisation number 829578352. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 189,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 189,000
Operating profit
NOK 121,000
Equity
NOK −605,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
55.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.7%
Weak
Equity as a share of total capital

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

Who owns TJØLLINGVEIEN 520 AS?

LIH EIENDOM AS
TJØLLINGVEIEN 520 AS
NOK 189,000 rev. · NOK 121,000 profit

TJØLLINGVEIEN 520 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TJØLLINGVEIEN 520 AS

Who owns TJØLLINGVEIEN 520 AS?

LIH EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TJØLLINGVEIEN 520 AS?

TJØLLINGVEIEN 520 AS had revenue of NOK 189,000 in 2025.

Where is TJØLLINGVEIEN 520 AS based?

TJØLLINGVEIEN 520 AS has its business address in Stavern.

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.