BIZTRAC BETA
Retail sale of other food

BIFFEN.NO AS

Org. no. 836200802 Limited company (AS) Fredrikstad Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 27,000
Operating profit NOK −111
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−111 kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-08-28.

BIFFEN.NO AS is registered as a limited company in Fredrikstad, Østfold with organisation number 836200802. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Er produksjon og salg av BBQ-krydder og -saus, samt catering-, grill- og BBQ-relaterte tjenester, og annen virksomhet som naturlig hører sammen med dette.”.

Key figures

Revenue
NOK 27,000
Operating profit
NOK −111
Equity
NOK 23,000
Est. value
NOK 20,000

Financial health · 2025

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

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

Who owns BIFFEN.NO AS?

DANIEL WEERASINGHE LIND
BIFFEN.NO AS
NOK 27,000 rev. · NOK −111 profit

BIFFEN.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIFFEN.NO AS

Who owns BIFFEN.NO AS?

DANIEL WEERASINGHE LIND is the largest registered owner, with 100.0%.

What is the revenue of BIFFEN.NO AS?

BIFFEN.NO AS had revenue of NOK 27,000.

Who is the general manager of BIFFEN.NO AS?

Daniel Weerasinghe Lind is registered as general manager of BIFFEN.NO AS.

Where is BIFFEN.NO AS based?

BIFFEN.NO AS has its business address in Kråkerøy.

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.