BIZTRAC BETA
Rental and operating of own or leased real estate

STEINKARGATA 22 AS

Org. no. 929915100 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 177,000
Operating profit NOK 30,000
Equity NOK −1.6m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).

STEINKARGATA 22 AS is registered as a limited company in Stavanger, Rogaland with organisation number 929915100. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 177,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 177,000
Operating profit
NOK 30,000
Equity
NOK −1.6m
Est. value
NOK 204,000

Financial health · 2025

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

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

Who owns STEINKARGATA 22 AS?

TERREBRUNE AS
STEINKARGATA 22 AS
NOK 177,000 rev. · NOK 30,000 profit

STEINKARGATA 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEINKARGATA 22 AS

Who owns STEINKARGATA 22 AS?

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

What is the revenue of STEINKARGATA 22 AS?

STEINKARGATA 22 AS had revenue of NOK 177,000 in 2025.

Who is the general manager of STEINKARGATA 22 AS?

Christian Talleraas is registered as general manager of STEINKARGATA 22 AS.

Where is STEINKARGATA 22 AS based?

STEINKARGATA 22 AS has its business address in Stavanger.

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.