biztrac. BETA
COMPANY REGISTER PROFILE
989017039 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

O C SMIDESANG HOLDING AS

Org. no. 989017039 Limited company (AS) Sel Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 6.7m
Incorporated 2005
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

O C SMIDESANG HOLDING AS is registered as a limited company in Sel, Innlandet with organisation number 989017039. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, drive, utvikle og investere i fast eiendom, verdipapirer og andre formuesobjekter.”.

Key figures · 2025

Operating profit
NOK −24,000
▲ +38 %
Equity
NOK 6.7m
▲ +9 %
Est. value
NOK 8.9m

Financial health · 2025

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

Who owns O C SMIDESANG HOLDING AS?

O C SMIDESANG HOLDING AS
· NOK −24,000 profit

O C SMIDESANG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does O C SMIDESANG HOLDING AS own?

O C SMIDESANG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about O C SMIDESANG HOLDING AS

Who owns O C SMIDESANG HOLDING AS?

Ole Christian Smidesang is the largest registered owner, with 100.0%.

Where is O C SMIDESANG HOLDING AS based?

O C SMIDESANG HOLDING AS has its business address in Otta.

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.