BIZTRAC BETA
Other real estate activities on a fee or contract basis

GULAG TAKST & EIENDOM AS

Org. no. 930726362 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 1.2m
Equity NOK 1.5m
Incorporated 2023
Share capital NOK 30,000

GULAG TAKST & EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 930726362. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Taksering, kjøp, drift og salg av eiendom og andre produkter, tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 1.2m
Equity
NOK 1.5m
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.6%
Satisfactory
Equity as a share of total capital

Who owns GULAG TAKST & EIENDOM AS?

GULAG HOLDING AS
GULAG TAKST & EIENDOM AS
NOK 3.4m rev. · NOK 1.2m profit

GULAG TAKST & EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULAG TAKST & EIENDOM AS

Who owns GULAG TAKST & EIENDOM AS?

GULAG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GULAG TAKST & EIENDOM AS?

GULAG TAKST & EIENDOM AS had revenue of NOK 3.4m in 2025.

Where is GULAG TAKST & EIENDOM AS based?

GULAG TAKST & EIENDOM AS has its business address in Tønsberg.

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.