biztrac. BETA
COMPANY REGISTER PROFILE
916235453 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other publishing activities, except software publishing

FLOKK DIGITAL AS

Org. no. 916235453 Limited company (AS) Bærum Incorporated 2015 Active
Operating profit NOK −12,000
Equity NOK 90,000
Incorporated 2015
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

FLOKK DIGITAL AS is registered as a limited company in Bærum, Akershus with organisation number 916235453. The business is classified under other publishing activities, except software publishing (NACE 58.190). The company was incorporated in 2015. Registered share capital is NOK 33,000, divided into 1112 shares. The company's stated purpose is: “Utvikling og produksjon av trykte og digitale reklame- og medieprodukter samt dertil hørende virksomhet.”.

Former names: FLOKK AS

Key figures · 2025

Operating profit
NOK −12,000
▲ +4 %
Equity
NOK 90,000
▼ −12 %
Est. value
NOK 164,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns FLOKK DIGITAL AS?

FLOKK DIGITAL AS
· NOK −12,000 profit

FLOKK DIGITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLOKK DIGITAL AS own?

FLOKK DIGITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLOKK DIGITAL AS

Who owns FLOKK DIGITAL AS?

Tomas Lien is the largest registered owner, with 100.0%.

Who is the general manager of FLOKK DIGITAL AS?

Tomas Lien is registered as general manager of FLOKK DIGITAL AS.

Where is FLOKK DIGITAL AS based?

FLOKK DIGITAL AS has its business address in Vøyenenga.

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.