biztrac. BETA
COMPANY REGISTER PROFILE
925827177 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Machining of metals

OAK RIDGE CAPITAL AS

Org. no. 925827177 Limited company (AS) Tønsberg Incorporated 2020 Active
Revenue 2025 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 26.3m
Incorporated 2020
Share capital NOK 170,000

OAK RIDGE CAPITAL AS is registered as a limited company in Tønsberg, Vestfold with organisation number 925827177. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2020. Registered share capital is NOK 170,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer og andeler i egne og andre selskaper samt finansielle instrumenter og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +130 %
Operating profit
NOK 1.4m
▲ +190 %
Equity
NOK 26.3m
▲ +30 %
Est. value
NOK 16.3m

Financial health · 2025

Liquidity
287.95
Very good
Current assets ÷ current liabilities
Profitability
6.5%
Satisfactory
Return on total assets
Solidity
98.5%
Very good
Equity as a share of total capital

Who owns OAK RIDGE CAPITAL AS?

OAK RIDGE CAPITAL AS
NOK 1.8m rev. · NOK 1.4m profit

OAK RIDGE CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OAK RIDGE CAPITAL AS own?

OAK RIDGE CAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OAK RIDGE CAPITAL AS

Who owns OAK RIDGE CAPITAL AS?

Edvin Syse is the largest registered owner, with 100.0%.

What is the revenue of OAK RIDGE CAPITAL AS?

OAK RIDGE CAPITAL AS had revenue of NOK 1.8m in 2025.

Where is OAK RIDGE CAPITAL AS based?

OAK RIDGE CAPITAL AS has its business address in Tønsberg.

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.