BIZTRAC BETA
Buying and selling of own real estate

TODOROKI AS

Org. no. 920133118 Limited company (AS) Frogn Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 3.5m
Incorporated 2017
Share capital NOK 30,000

Signals

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

TODOROKI AS is registered as a limited company in Frogn, Akershus with organisation number 920133118. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 3.5m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns TODOROKI AS?

ROAR BJERKE
TODOROKI AS
NOK 0 rev. · NOK −6,000 profit

TODOROKI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TODOROKI AS own?

TODOROKI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TODOROKI AS

Who owns TODOROKI AS?

ROAR BJERKE is the largest registered owner, with 100.0%.

What is the revenue of TODOROKI AS?

TODOROKI AS had revenue of NOK 0 in 2024.

Who is the general manager of TODOROKI AS?

Roar Bjerke is registered as general manager of TODOROKI AS.

Where is TODOROKI AS based?

TODOROKI AS has its business address in Nordre Frogn.

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.