BIZTRAC BETA
Manufacture of batteries and accumulators

BRYTE AS

Org. no. 824811652 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK −2.0m
Equity NOK 2.1m
Incorporated 2020
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,0 mill kr).

BRYTE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 824811652. The business is classified under manufacture of batteries and accumulators (NACE 27.200). The company was incorporated in 2020. Registered share capital is NOK 1.0m, divided into 34706309 shares. The company's stated purpose is: “Utvikler, produserer, selger og drifter batterier til små- og storskala energilagring. Konsulenttjenester innenfor overnevnte fagfelt og annet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK −2.0m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK −2.0m
Equity
NOK 2.1m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns BRYTE AS?

OPTIFLEX AS
BRYTE AS
NOK 4.6m rev. · NOK −2.0m profit

BRYTE AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does BRYTE AS own?

BRYTE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRYTE AS

Who owns BRYTE AS?

OPTIFLEX AS is the largest registered owner, with 13.7%.

What is the revenue of BRYTE AS?

BRYTE AS had revenue of NOK 4.6m in 2024.

Who is the general manager of BRYTE AS?

Ask Ibsen Lindal is registered as general manager of BRYTE AS.

Where is BRYTE AS based?

BRYTE AS has its business address in Trondheim.

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.