biztrac. BETA
COMPANY REGISTER PROFILE
988201855 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

ØVRE ULLERN TERRASSE 3 AS

Org. no. 988201855 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −285,000
Equity NOK 159,000
Incorporated 2005
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−285k kr).

ØVRE ULLERN TERRASSE 3 AS is registered as a limited company in Oslo, Oslo with organisation number 988201855. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 400000 shares. The company's stated purpose is: “Eiendomsutvikling og eiendomsdrift, herunder erverv, utvikling, drift, salg og utleie av fast eiendom.Det skal være anledning til å eie aksjer og andeler i andre selskaper, samt hva herved naturlig står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −285,000
▼ −6 %
Equity
NOK 159,000
▼ −64 %
Est. value
NOK 145,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
1.3%
Not satisfactory
Equity as a share of total capital

Who owns ØVRE ULLERN TERRASSE 3 AS?

ØVRE ULLERN TERRASSE 3 AS
· NOK −285,000 profit

ØVRE ULLERN TERRASSE 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØVRE ULLERN TERRASSE 3 AS

Who owns ØVRE ULLERN TERRASSE 3 AS?

KATH AS is the largest registered owner, with 100.0%.

Who is the general manager of ØVRE ULLERN TERRASSE 3 AS?

Bård Ottar Wendelborg is registered as general manager of ØVRE ULLERN TERRASSE 3 AS.

Where is ØVRE ULLERN TERRASSE 3 AS based?

ØVRE ULLERN TERRASSE 3 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.