BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

KBI DESIGN AS

Org. no. 977276004 Limited company (AS) Vestby Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −382,000
Equity NOK 310,000
Incorporated 1997
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−382k kr).

KBI DESIGN AS is registered as a limited company in Vestby, Akershus with organisation number 977276004. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Drive design, kjøp og salg av møbler og interiør-/eksteriørartikler, samt kjøp og salg av eiendom og hva som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −382,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −382,000
Equity
NOK 310,000
Est. value
NOK 653,000

Financial health · 2025

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

Who owns KBI DESIGN AS?

ØYSTEIN GRESBERG
KBI DESIGN AS
NOK 1.6m rev. · NOK −382,000 profit

KBI DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KBI DESIGN AS

Who owns KBI DESIGN AS?

ØYSTEIN GRESBERG is the largest registered owner, with 100.0%.

What is the revenue of KBI DESIGN AS?

KBI DESIGN AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KBI DESIGN AS?

Øystein Gresberg is registered as general manager of KBI DESIGN AS.

Where is KBI DESIGN AS based?

KBI DESIGN AS has its business address in Vestby.

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.