BIZTRAC BETA
Business and other management consultancy activities

TERIAK AS

Org. no. 920985173 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 711,000
Equity NOK 2.1m
Incorporated 2018
Employees 10
Share capital NOK 100,000

TERIAK AS is registered as a limited company in Oslo, Oslo with organisation number 920985173. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av rådgivningstjenester og utleie av personell til aktører innen helseområdet og dertil naturlig tilhørende virksomhet, samt kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK 711,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 711,000
Equity
NOK 2.1m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns TERIAK AS?

KEN TESAKER
TERIAK AS
NOK 13.3m rev. · NOK 711,000 profit

TERIAK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TERIAK AS own?

TERIAK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TERIAK AS

Who owns TERIAK AS?

KEN TESAKER is the largest registered owner, with 100.0%.

What is the revenue of TERIAK AS?

TERIAK AS had revenue of NOK 13.3m in 2024.

Who is the general manager of TERIAK AS?

Ken Tesaker is registered as general manager of TERIAK AS.

Where is TERIAK AS based?

TERIAK 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.