BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

WHITEBOARD INVEST AS

Org. no. 925401145 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 379,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

WHITEBOARD INVEST AS is registered as a limited company in Frogn, Akershus with organisation number 925401145. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tilby datatjenester, lagring, konsulentvirksomhet, rådgivning og annen virksomhet som naturlig hører til herunder. Selskapet vil også investere i andre foretak samt eiendom.”.

Key figures · 2024

Operating profit
NOK −24,000
Equity
NOK 379,000
Est. value
NOK 688,000

Financial health · 2024

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

Who owns WHITEBOARD INVEST AS?

CHRISTIAN FALCH
WHITEBOARD INVEST AS
· NOK −24,000 profit

WHITEBOARD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WHITEBOARD INVEST AS own?

WHITEBOARD INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WHITEBOARD INVEST AS

Who owns WHITEBOARD INVEST AS?

CHRISTIAN FALCH is the largest registered owner, with 100.0%.

Who is the general manager of WHITEBOARD INVEST AS?

Christian Falch is registered as general manager of WHITEBOARD INVEST AS.

Where is WHITEBOARD INVEST AS based?

WHITEBOARD INVEST AS has its business address in Drøbak.

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.