BIZTRAC BETA
Development of building projects

ØVRE SVERRESBORG AS

Org. no. 918764887 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −157,000
Equity NOK −737,000
Incorporated 2017
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−737k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−157k kr).

ØVRE SVERRESBORG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918764887. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −157,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −157,000
Equity
NOK −737,000

Financial health · 2025

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

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

Who owns ØVRE SVERRESBORG AS?

SILVA UTVIKLING AS
ØVRE SVERRESBORG AS
NOK 0 rev. · NOK −157,000 profit

ØVRE SVERRESBORG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØVRE SVERRESBORG AS

Who owns ØVRE SVERRESBORG AS?

SILVA UTVIKLING AS is the largest registered owner, with 75.0%.

What is the revenue of ØVRE SVERRESBORG AS?

ØVRE SVERRESBORG AS had revenue of NOK 0 in 2025.

Who is the general manager of ØVRE SVERRESBORG AS?

Per Erik Austberg is registered as general manager of ØVRE SVERRESBORG AS.

Where is ØVRE SVERRESBORG AS based?

ØVRE SVERRESBORG AS has its business address in Heimdal.

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.