BIZTRAC BETA
Rental and operating of own or leased real estate

INN-BOKS AS

Org. no. 910695703 Limited company (AS) Kristiansand Incorporated 1968 Active
Ownership graph ↗
Revenue 2024 NOK 67.6m
Operating profit NOK 12.8m
Equity NOK 5.2m
Incorporated 1968
Share capital NOK 525,000

Signals

1 flags
  • Nylig endring 2026-03-19 Adresseendring registrert 2026-03-19.

INN-BOKS AS is registered as a limited company in Kristiansand, Agder with organisation number 910695703. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1968. Registered share capital is NOK 525,000. The company's stated purpose is: “Investering i eiendom og andre selskaper, utleie av fast eiendom, samt annen økonomisk virksomhet som naturlig ligger under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 67.6m in revenue and NOK 12.8m in operating profit.

Key figures · 2024

Revenue
NOK 67.6m
Operating profit
NOK 12.8m
Equity
NOK 5.2m
Est. value
NOK 34.5m

Financial health · 2024

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

Who owns INN-BOKS AS?

MESTERBYGG KRISTIANSAND AS
INN-BOKS AS
NOK 67.6m rev. · NOK 12.8m profit

INN-BOKS AS has 2 registered shareholders:

All shareholders and roles →

Group structure

INN-BOKS AS er morselskap for 2 datterselskaper:

Frequently asked questions about INN-BOKS AS

Who owns INN-BOKS AS?

MESTERBYGG KRISTIANSAND AS is the largest registered owner, with 66.7%.

What is the revenue of INN-BOKS AS?

INN-BOKS AS had revenue of NOK 67.6m in 2024.

Who is the general manager of INN-BOKS AS?

Preben Langeland is registered as general manager of INN-BOKS AS.

Where is INN-BOKS AS based?

INN-BOKS AS has its business address in Kristiansand S.

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.