BIZTRAC BETA
Other technical consultancy

ODDSTEN CONSULTING AS

Org. no. 931364510 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 927,000
Equity NOK 578,000
Incorporated 2023
Share capital NOK 30,000

ODDSTEN CONSULTING AS is registered as a limited company in Asker, Akershus with organisation number 931364510. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen rådgivning/konsulenttjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 927,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 927,000
Equity
NOK 578,000
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ODDSTEN CONSULTING AS?

KRISTIAN ODDSTEN
ODDSTEN CONSULTING AS
NOK 1.2m rev. · NOK 927,000 profit

ODDSTEN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODDSTEN CONSULTING AS

Who owns ODDSTEN CONSULTING AS?

KRISTIAN ODDSTEN is the largest registered owner, with 100.0%.

What is the revenue of ODDSTEN CONSULTING AS?

ODDSTEN CONSULTING AS had revenue of NOK 1.2m in 2025.

Who is the general manager of ODDSTEN CONSULTING AS?

Kristian Oddsten is registered as general manager of ODDSTEN CONSULTING AS.

Where is ODDSTEN CONSULTING AS based?

ODDSTEN CONSULTING AS has its business address in Nesbru.

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.