BIZTRAC BETA
Painting and glazing

TELEMARKSPRO AS

Org. no. 931769529 Limited company (AS) Midt-Telemark Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK −35,000
Equity NOK 293,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−35k kr).

TELEMARKSPRO AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 931769529. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Malerarbeid og snekkertjenester, samt andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK −35,000
Equity
NOK 293,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns TELEMARKSPRO AS?

KRISTIAN ALFREDO PEDERSEN
TELEMARKSPRO AS
NOK 3.8m rev. · NOK −35,000 profit

TELEMARKSPRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TELEMARKSPRO AS

Who owns TELEMARKSPRO AS?

KRISTIAN ALFREDO PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TELEMARKSPRO AS?

TELEMARKSPRO AS had revenue of NOK 3.8m in 2024.

Who is the general manager of TELEMARKSPRO AS?

Kristian Alfredo Pedersen is registered as general manager of TELEMARKSPRO AS.

Where is TELEMARKSPRO AS based?

TELEMARKSPRO AS has its business address in Bø I Telemark.

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.