BIZTRAC BETA
Computer programming activities

BIRDFLOCKS AS

Org. no. 925913243 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −131,000
Equity NOK −89,000
Incorporated 2020
Share capital NOK 36,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−89k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−131k kr).
  • Nylig endring 2026-03-12 Adresseendring registrert 2026-03-12.

BIRDFLOCKS AS is registered as a limited company in Asker, Akershus with organisation number 925913243. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 36,000, divided into 30000 shares. The company's stated purpose is: “Utvikle og tilby teknologiløsninger som hjelper ulike virksomheter å samarbeide bedre på ulike nivå. BirdFlocks AS skal også utvikle andre innovasjoner innen samhandling bredt forstått. BirdFlocks kan også gjøre annen virksomhet som er relatert til dette. Selskapet kan eie aksjer og eiendom. ”.

Key figures · 2024

Operating profit
NOK −131,000
Equity
NOK −89,000

Financial health · 2024

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

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

Who owns BIRDFLOCKS AS?

VMR AS
BIRDFLOCKS AS
· NOK −131,000 profit

BIRDFLOCKS AS has 15 registered shareholders:

All shareholders and roles →

Which companies does BIRDFLOCKS AS own?

BIRDFLOCKS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BIRDFLOCKS AS

Who owns BIRDFLOCKS AS?

VMR AS is the largest registered owner, with 55.9%.

Where is BIRDFLOCKS AS based?

BIRDFLOCKS AS has its business address in Asker.

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.