BIZTRAC BETA
Development of building projects

TVERRBAKKEN AS

Org. no. 919219408 Limited company (AS) Vennesla Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 132,000
Operating profit NOK 71,000
Equity NOK −548,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

TVERRBAKKEN AS is registered as a limited company in Vennesla, Agder with organisation number 919219408. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling av tomteområdet, samt eie, utleie og bygging av eiendom og ellers delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 132,000 in revenue and NOK 71,000 in operating profit.

Key figures · 2025

Revenue
NOK 132,000
Operating profit
NOK 71,000
Equity
NOK −548,000
Est. value
NOK 486,000

Financial health · 2025

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

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

Who owns TVERRBAKKEN AS?

SØRHEIM EIERSELSKAP AS
TVERRBAKKEN AS
NOK 132,000 rev. · NOK 71,000 profit

TVERRBAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TVERRBAKKEN AS

Who owns TVERRBAKKEN AS?

SØRHEIM EIERSELSKAP AS is the largest registered owner, with 50.0%.

What is the revenue of TVERRBAKKEN AS?

TVERRBAKKEN AS had revenue of NOK 132,000 in 2025.

Where is TVERRBAKKEN AS based?

TVERRBAKKEN AS has its business address in Øvrebø.

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.