biztrac. BETA
COMPANY REGISTER PROFILE
934288173 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GJØA O701 AS

Org. no. 934288173 Limited company (AS) Tromsø Incorporated 2024 Active
Revenue 2025 NOK 297,000
Operating profit NOK 179,000
Equity NOK −244,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

GJØA O701 AS is registered as a limited company in Tromsø, Troms with organisation number 934288173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 297,000 in revenue and NOK 179,000 in operating profit.

Key figures · 2025

Revenue
NOK 297,000
Operating profit
NOK 179,000
▲ +228 %
Equity
NOK −244,000
▼ −72 %
Est. value
NOK 353,000

Financial health · 2025

Liquidity
5.32
Very good
Current assets ÷ current liabilities
Profitability
4.3%
Weak
Return on total assets
Solidity
-5.8%
Weak
Equity as a share of total capital

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

Who owns GJØA O701 AS?

GJØA O701 AS
NOK 297,000 rev. · NOK 179,000 profit

GJØA O701 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJØA O701 AS

Who owns GJØA O701 AS?

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

What is the revenue of GJØA O701 AS?

GJØA O701 AS had revenue of NOK 297,000 in 2025.

Who is the general manager of GJØA O701 AS?

Harald Audun Solvang is registered as general manager of GJØA O701 AS.

Where is GJØA O701 AS based?

GJØA O701 AS has its business address in Tromsø.

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.