BIZTRAC BETA
Other technical consultancy

NYBAKK CONSULTING AS

Org. no. 921693133 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 17,000
Equity NOK 1.7m
Incorporated 2018
Share capital NOK 30,000

NYBAKK CONSULTING AS is registered as a limited company in Bergen, Vestland with organisation number 921693133. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen teknisk og administrativ konsulentvirksomhet - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 17,000
Equity
NOK 1.7m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns NYBAKK CONSULTING AS?

BJØRN JOHNNY NYBAKK
NYBAKK CONSULTING AS
NOK 1.0m rev. · NOK 17,000 profit

NYBAKK CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYBAKK CONSULTING AS

Who owns NYBAKK CONSULTING AS?

BJØRN JOHNNY NYBAKK is the largest registered owner, with 100.0%.

What is the revenue of NYBAKK CONSULTING AS?

NYBAKK CONSULTING AS had revenue of NOK 1.0m in 2024.

Who is the general manager of NYBAKK CONSULTING AS?

Bjørn Johnny Nybakk is registered as general manager of NYBAKK CONSULTING AS.

Where is NYBAKK CONSULTING AS based?

NYBAKK CONSULTING AS has its business address in Fana.

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.