BIZTRAC BETA
Construction of residential and non-residential buildings

OKS-TJENESTER AS

Org. no. 918598103 Limited company (AS) Stjørdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 15.0m
Operating profit NOK 380,000
Equity NOK 186,000
Incorporated 2017
Employees 5
Share capital NOK 60,000

OKS-TJENESTER AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 918598103. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017 and has 5 registered employees. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg, samt kjøp, salg og utleie av fast eiendom og det som naturlig følger med slik virksomhet, samt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.0m in revenue and NOK 380,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.0m
Operating profit
NOK 380,000
Equity
NOK 186,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.8%
Weak
Equity as a share of total capital

Who owns OKS-TJENESTER AS?

OLE KRISTIAN SÆTRAN
OKS-TJENESTER AS
NOK 15.0m rev. · NOK 380,000 profit

OKS-TJENESTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OKS-TJENESTER AS

Who owns OKS-TJENESTER AS?

OLE KRISTIAN SÆTRAN is the largest registered owner, with 80.0%.

What is the revenue of OKS-TJENESTER AS?

OKS-TJENESTER AS had revenue of NOK 15.0m in 2024.

Who is the general manager of OKS-TJENESTER AS?

Ole Kristian Sætran is registered as general manager of OKS-TJENESTER AS.

Where is OKS-TJENESTER AS based?

OKS-TJENESTER AS has its business address in Hegra.

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.