BIZTRAC BETA
Publishing of books

TELEMARK STORIES AS

Org. no. 931495534 Limited company (AS) Tinn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 275,000
Operating profit NOK 42,000
Equity NOK 125,000
Incorporated 2023
Share capital NOK 60,000

TELEMARK STORIES AS is registered as a limited company in Tinn, Telemark with organisation number 931495534. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Utvikling av historiske barnebøker, film, TV-serier, spill og andre interaktive læringsplattformer, basert på deler av Telemarks historie og alt som står i sammenheng med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 275,000 in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 275,000
Operating profit
NOK 42,000
Equity
NOK 125,000
Est. value
NOK 318,000

Financial health · 2025

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

Who owns TELEMARK STORIES AS?

BJØRN STEINAR IVERSEN
TELEMARK STORIES AS
NOK 275,000 rev. · NOK 42,000 profit

TELEMARK STORIES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TELEMARK STORIES AS

Who owns TELEMARK STORIES AS?

BJØRN STEINAR IVERSEN is the largest registered owner, with 50.0%.

What is the revenue of TELEMARK STORIES AS?

TELEMARK STORIES AS had revenue of NOK 275,000 in 2025.

Who is the general manager of TELEMARK STORIES AS?

Bjørn Steinar Iversen is registered as general manager of TELEMARK STORIES AS.

Where is TELEMARK STORIES AS based?

TELEMARK STORIES AS has its business address in Rjukan.

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.