BIZTRAC BETA
Performing arts activities in dramatic arts

DIGT OG FORBANNET LØGN AS

Org. no. 998241537 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 80,000
Operating profit NOK 44,000
Equity NOK 176,000
Incorporated 2012
Share capital NOK 30,000

DIGT OG FORBANNET LØGN AS is registered as a limited company in Oslo, Oslo with organisation number 998241537. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling, planlegging, utførelse av scenekunst, foredrag, kurs/undervisning for privat eller offentlig næringsliv/virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 80,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 80,000
Operating profit
NOK 44,000
Equity
NOK 176,000
Est. value
NOK 238,000

Financial health · 2025

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

Who owns DIGT OG FORBANNET LØGN AS?

FRANK JØRSTAD
DIGT OG FORBANNET LØGN AS
NOK 80,000 rev. · NOK 44,000 profit

DIGT OG FORBANNET LØGN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIGT OG FORBANNET LØGN AS own?

DIGT OG FORBANNET LØGN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DIGT OG FORBANNET LØGN AS

Who owns DIGT OG FORBANNET LØGN AS?

FRANK JØRSTAD is the largest registered owner, with 100.0%.

What is the revenue of DIGT OG FORBANNET LØGN AS?

DIGT OG FORBANNET LØGN AS had revenue of NOK 80,000 in 2025.

Where is DIGT OG FORBANNET LØGN AS based?

DIGT OG FORBANNET LØGN AS has its business address in Oslo.

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.