biztrac. BETA
COMPANY REGISTER PROFILE
936495745 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

UNDERTEKST AS

Org. no. 936495745 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.0m
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-01.

UNDERTEKST AS is registered as a limited company in Oslo, Oslo with organisation number 936495745. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon av innhold for TV, podcast, scene og internett.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 1.0m
Equity
NOK 30,000
Est. value
NOK 3.2m

Financial health · 2025

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

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

Who owns UNDERTEKST AS?

UNDERTEKST AS
NOK 1.5m rev. · NOK 1.0m profit

UNDERTEKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UNDERTEKST AS

Who owns UNDERTEKST AS?

Harald Meldal Eia is the largest registered owner, with 50.0%.

What is the revenue of UNDERTEKST AS?

UNDERTEKST AS had revenue of NOK 1.5m in 2025.

Who is the general manager of UNDERTEKST AS?

Harald Meldal Eia is registered as general manager of UNDERTEKST AS.

Where is UNDERTEKST AS based?

UNDERTEKST 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 03.10.2026.

Report a problem

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