BIZTRAC BETA
COMPANY REGISTER PROFILE
929169425 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TOFFELOFFE AS

Org. no. 929169425 Limited company (AS) Eidsvoll Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 9,000
Incorporated 2022
Share capital NOK 30,000

TOFFELOFFE AS is registered as a limited company in Eidsvoll, Akershus with organisation number 929169425. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendommer.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 9,000
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns TOFFELOFFE AS?

TOFFELOFFE AS
· NOK 0 profit

TOFFELOFFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOFFELOFFE AS

Who owns TOFFELOFFE AS?

KRISTOFFER GJØDINGSETER is the largest registered owner, with 100.0%.

Who is the general manager of TOFFELOFFE AS?

Kristoffer Gjødingseter is registered as general manager of TOFFELOFFE AS.

Where is TOFFELOFFE AS based?

TOFFELOFFE AS has its business address in Dal.

Property

Business address c/o Kristoffer Gjødingseter Normann Hjelles veg 29, 2072 Dal
Cadastral unit 3240-88/221/0/0
Building Tomannsbolig, vertikal · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.