biztrac. BETA
COMPANY REGISTER PROFILE
914315654 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of furniture

NYBO KJØKKEN AS

Org. no. 914315654 Limited company (AS) Ringerike Incorporated 2014 Active
Revenue 2025 NOK 32.0m
Operating profit NOK −2.6m
Equity NOK −2.7m
Incorporated 2014
Employees 16
Share capital NOK 1.1m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,7 mill kr).

NYBO KJØKKEN AS is registered as a limited company in Ringerike, Buskerud with organisation number 914315654. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2014 and has 16 registered employees. Registered share capital is NOK 1.1m, divided into 4312 shares. The company's stated purpose is: “Handel og produksjon av trevarer og hva som følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.0m in revenue and NOK −2.6m in operating profit.

Key figures · 2025

Revenue
NOK 32.0m
▼ −5 %
Operating profit
NOK −2.6m
▼ −85 %
Equity
NOK −2.7m
▼ −362 %

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
-16.5%
Not satisfactory
Return on total assets
Solidity
-17.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NYBO KJØKKEN AS?

NYBO KJØKKEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about NYBO KJØKKEN AS

Who owns NYBO KJØKKEN AS?

BJØRKA AS is the largest registered owner, with 66.2%.

What is the revenue of NYBO KJØKKEN AS?

NYBO KJØKKEN AS had revenue of NOK 32.0m in 2025.

Who is the general manager of NYBO KJØKKEN AS?

Frode Tangen is registered as general manager of NYBO KJØKKEN AS.

Where is NYBO KJØKKEN AS based?

NYBO KJØKKEN AS has its business address in Tyristrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.