biztrac. BETA
COMPANY REGISTER PROFILE
935678374 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TRANBERG SERVICE OG VEDLIKEHOLD AS

Org. no. 935678374 Limited company (AS) Gjøvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 403,000
Equity NOK 353,000
Incorporated 2025
Employees 30
Share capital NOK 30,000

TRANBERG SERVICE OG VEDLIKEHOLD AS is registered as a limited company in Gjøvik, Innlandet with organisation number 935678374. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025 and has 30 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 403,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 403,000
Equity
NOK 353,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
35.5%
Good
Equity as a share of total capital

Who owns TRANBERG SERVICE OG VEDLIKEHOLD AS?

TRANBERG SERVICE OG VEDLIKEHOLD AS
NOK 4.6m rev. · NOK 403,000 profit

TRANBERG SERVICE OG VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRANBERG SERVICE OG VEDLIKEHOLD AS

Who owns TRANBERG SERVICE OG VEDLIKEHOLD AS?

Kristian Amundsen Tranberg is the largest registered owner, with 100.0%.

What is the revenue of TRANBERG SERVICE OG VEDLIKEHOLD AS?

TRANBERG SERVICE OG VEDLIKEHOLD AS had revenue of NOK 4.6m in 2025.

Where is TRANBERG SERVICE OG VEDLIKEHOLD AS based?

TRANBERG SERVICE OG VEDLIKEHOLD AS has its business address in Biristrand.

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.