BIZTRAC BETA
TAKK AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Restaurant activities

TAKK AS

Org. no. 933142612 Limited company (AS) Fredrikstad Incorporated 2024 Bankrupt
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 80,000
Equity NOK 54,000
Incorporated 2024
Employees 16
Share capital NOK 30,000

Signals

2 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Nylig endring 2026-07-28 Konkurs registrert 2026-07-28.

TAKK AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933142612. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive en restaurant eller kafé, inkludert, men ikke begrenset til, salg av mat- og drikkevarer for konsum på stedet, take-away og eventuell levering.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 80,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 80,000
Equity
NOK 54,000
Est. value
NOK 224,000

Financial health · 2024

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

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

Who owns TAKK AS?

LEBRI HOLDING AS
TAKK AS
NOK 6.8m rev. · NOK 80,000 profit

TAKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAKK AS

Who owns TAKK AS?

LEBRI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TAKK AS?

TAKK AS had revenue of NOK 6.8m in 2024.

Where is TAKK AS based?

TAKK AS has its business address in Fredrikstad.

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.