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

S703 HOLDING AS

Org. no. 922582181 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.9m
Equity NOK −13.9m
Incorporated 2019
Share capital NOK 30,000

Signals

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

S703 HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 922582181. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive virksomhet med fast eiendom, herunder direkte og indirekte, å eie, drive og selge fast eiendom, samt annen virksomhet som naturlig faller inn under denne beskrivelsen.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.9m
▲ +3406 %
Equity
NOK −13.9m
▼ −245 %
Est. value
NOK 6.9m

Financial health · 2025

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
15.7%
Very good
Return on total assets
Solidity
-251.5%
Weak
Equity as a share of total capital

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

Who owns S703 HOLDING AS?

S703 HOLDING AS
NOK 2.6m rev. · NOK 1.9m profit

S703 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S703 HOLDING AS

Who owns S703 HOLDING AS?

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

What is the revenue of S703 HOLDING AS?

S703 HOLDING AS had revenue of NOK 2.6m in 2025.

Where is S703 HOLDING AS based?

S703 HOLDING 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.