BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

TOFTEBERG AS

Org. no. 927085755 Limited company (AS) Råde Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK −170,000
Equity NOK 59,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

TOFTEBERG AS is registered as a limited company in Råde, Østfold with organisation number 927085755. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av «gjør det selv» lekeapparater, boder, grillhus, gapahuk og andre utomhus produkter knyttet til hjem og fritid.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK −170,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK −170,000
Equity
NOK 59,000
Est. value
NOK 3.2m

Financial health · 2024

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

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

Who owns TOFTEBERG AS?

TED ØISTEIN NILSEN
TOFTEBERG AS
NOK 6.2m rev. · NOK −170,000 profit

TOFTEBERG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOFTEBERG AS

Who owns TOFTEBERG AS?

TED ØISTEIN NILSEN is the largest registered owner, with 50.0%.

What is the revenue of TOFTEBERG AS?

TOFTEBERG AS had revenue of NOK 6.2m in 2024.

Who is the general manager of TOFTEBERG AS?

Ted Øistein Nilsen is registered as general manager of TOFTEBERG AS.

Where is TOFTEBERG AS based?

TOFTEBERG AS has its business address in Råde.

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.