BIZTRAC BETA
Business and other management consultancy activities

IBOKS INVEST AS

Org. no. 986530460 Limited company (AS) Sandnes Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 883,000
Operating profit NOK 409,000
Equity NOK 2.8m
Incorporated 2004
Share capital NOK 100,000

IBOKS INVEST AS is registered as a limited company in Sandnes, Rogaland with organisation number 986530460. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bedriftsrådgivning, prosjektutvikling, prosjektledelse, kjøp, salg og utleie av fast eiendom og hva som hermed står i forbindelse, samt å delta som aksjonær eller på annen måte ved investering i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 883,000 in revenue and NOK 409,000 in operating profit.

Key figures · 2025

Revenue
NOK 883,000
Operating profit
NOK 409,000
Equity
NOK 2.8m
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.2%
Good
Equity as a share of total capital

Who owns IBOKS INVEST AS?

GUTTORM SKRETTING
IBOKS INVEST AS
NOK 883,000 rev. · NOK 409,000 profit

IBOKS INVEST AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about IBOKS INVEST AS

Who owns IBOKS INVEST AS?

GUTTORM SKRETTING is the largest registered owner, with 24.0%.

What is the revenue of IBOKS INVEST AS?

IBOKS INVEST AS had revenue of NOK 883,000 in 2025.

Who is the general manager of IBOKS INVEST AS?

Guttorm Skretting is registered as general manager of IBOKS INVEST AS.

Where is IBOKS INVEST AS based?

IBOKS INVEST AS has its business address in Sandnes.

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.