biztrac. BETA
COMPANY REGISTER PROFILE
913450671 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of information and communication equipment

GRIPTEL AS

Org. no. 913450671 Limited company (AS) Bærum Incorporated 2014 Active
Revenue 2025 NOK 49.9m
Operating profit NOK −10.3m
Equity NOK 10.4m
Incorporated 2014
Employees 7
Share capital NOK 13.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10,3 mill kr).

GRIPTEL AS is registered as a limited company in Bærum, Akershus with organisation number 913450671. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2014 and has 7 registered employees. Registered share capital is NOK 13.4m, divided into 134139 shares. The company's stated purpose is: “Utvikling, produksjon og salg av stålelementer, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 49.9m in revenue and NOK −10.3m in operating profit.

Key figures · 2025

Revenue
NOK 49.9m
▼ −31 %
Operating profit
NOK −10.3m
▼ −330 %
Equity
NOK 10.4m
▼ −72 %
Est. value
NOK 15.7m

Financial health · 2025

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
-18.0%
Not satisfactory
Return on total assets
Solidity
32.0%
Good
Equity as a share of total capital

Who owns GRIPTEL AS?

GRIPTEL AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRIPTEL AS

Who owns GRIPTEL AS?

AVANT VENTURE CAPITAL AS is the largest registered owner, with 32.2%.

What is the revenue of GRIPTEL AS?

GRIPTEL AS had revenue of NOK 49.9m in 2025.

Who is the general manager of GRIPTEL AS?

Magnus Ove Johansson-Fornell is registered as general manager of GRIPTEL AS.

Where is GRIPTEL AS based?

GRIPTEL AS has its business address in Lysaker.

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.