BIZTRAC BETA
Computer consultancy and computer facilities management activities

GRYTBAK CONSULT AS

Org. no. 926476289 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 982,000
Equity NOK 1.3m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-15 Adresseendring registrert 2026-05-15.

GRYTBAK CONSULT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 926476289. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Datakonsulent-virksomhet og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 982,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 982,000
Equity
NOK 1.3m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns GRYTBAK CONSULT AS?

ESPEN GRYTBAK
GRYTBAK CONSULT AS
NOK 2.6m rev. · NOK 982,000 profit

GRYTBAK CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRYTBAK CONSULT AS

Who owns GRYTBAK CONSULT AS?

ESPEN GRYTBAK is the largest registered owner, with 100.0%.

What is the revenue of GRYTBAK CONSULT AS?

GRYTBAK CONSULT AS had revenue of NOK 2.6m in 2025.

Who is the general manager of GRYTBAK CONSULT AS?

Espen Grytbak is registered as general manager of GRYTBAK CONSULT AS.

Where is GRYTBAK CONSULT AS based?

GRYTBAK CONSULT AS has its business address in Strømmen.

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.