BIZTRAC BETA
Other captive investment companies

PER ODD SALBERG AS

Org. no. 988713872 Limited company (AS) Steinkjer Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −68,000
Equity NOK 9.4m
Incorporated 2005
Share capital NOK 157,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−68k kr).

PER ODD SALBERG AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 988713872. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 157,000, divided into 563 shares. The company's stated purpose is: “Selskapets formål er å forestå investering i selskaper og bygninger, investering i verdipapirer samt annet som naturlig har forbindelse med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −68,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −68,000
Equity
NOK 9.4m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns PER ODD SALBERG AS?

PER ODD SALBERG
PER ODD SALBERG AS
NOK 0 rev. · NOK −68,000 profit

PER ODD SALBERG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER ODD SALBERG AS own?

PER ODD SALBERG AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PER ODD SALBERG AS

Who owns PER ODD SALBERG AS?

PER ODD SALBERG is the largest registered owner, with 100.0%.

What is the revenue of PER ODD SALBERG AS?

PER ODD SALBERG AS had revenue of NOK 0 in 2025.

Where is PER ODD SALBERG AS based?

PER ODD SALBERG AS has its business address in Steinkjer.

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.