biztrac. BETA
COMPANY REGISTER PROFILE
999643671 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

BRIK AS

Org. no. 999643671 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 73,000
Equity NOK −279,000
Incorporated 2013
Employees 12
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−279k kr).

BRIK AS is registered as a limited company in Bergen, Vestland with organisation number 999643671. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2013 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikle og selge programvare og tilhørende tjenester, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 73,000 in operating profit.

Former names: BRIK VIDEOBASE AS

Key figures · 2025

Revenue
NOK 1.9m
▼ −24 %
Operating profit
NOK 73,000
▲ +25 %
Equity
NOK −279,000
▲ +15 %

Financial health · 2025

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
20.0%
Very good
Return on total assets
Solidity
-83.1%
Weak
Equity as a share of total capital

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

Who owns BRIK AS?

BRIK AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRIK AS

Who owns BRIK AS?

Bertin Holme Flatebø is the largest registered owner, with 59.4%.

What is the revenue of BRIK AS?

BRIK AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BRIK AS?

Bertin Holme Flatebø is registered as general manager of BRIK AS.

Where is BRIK AS based?

BRIK AS has its business address in Bergen.

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.