BIZTRAC BETA
Buying and selling of own real estate

SELSAAS AS

Org. no. 989847147 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 3.1m
Incorporated 2006
Share capital NOK 100,000

Signals

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

SELSAAS AS is registered as a limited company in Oslo, Oslo with organisation number 989847147. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å etablere andre selskap og å eie aksjer i andre selskap, samt hva herved står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 3.1m
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
84.0%
Very good
Equity as a share of total capital

Who owns SELSAAS AS?

ROBERT SELSAAS
SELSAAS AS
NOK 0 rev. · NOK −2,000 profit

SELSAAS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SELSAAS AS own?

SELSAAS AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about SELSAAS AS

Who owns SELSAAS AS?

ROBERT SELSAAS is the largest registered owner, with 100.0%.

What is the revenue of SELSAAS AS?

SELSAAS AS had revenue of NOK 0 in 2024.

Who is the general manager of SELSAAS AS?

Robert Selsaas is registered as general manager of SELSAAS AS.

Where is SELSAAS AS based?

SELSAAS 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 15.06.2026.

Report a problem

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