biztrac. BETA
COMPANY REGISTER PROFILE
935229987 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

MIN-TAKST AS

Org. no. 935229987 Limited company (AS) Gjerdrum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK −1.8m
Operating profit NOK −2.6m
Equity NOK 2.0m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,6 mill kr).

MIN-TAKST AS is registered as a limited company in Gjerdrum, Akershus with organisation number 935229987. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Boligtakst og konsulentvirksomhet innen byggesaker.”. The most recent filed accounts, for the 2025 financial year, show NOK −1.8m in revenue and NOK −2.6m in operating profit.

Key figures · 2025

Revenue
NOK −1.8m
▼ −166 %
Operating profit
NOK −2.6m
▼ −230 %
Equity
NOK 2.0m
▲ +0 %
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns MIN-TAKST AS?

MIN-TAKST AS
NOK −1.8m rev. · NOK −2.6m profit

MIN-TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIN-TAKST AS

Who owns MIN-TAKST AS?

Ernestas Liobikas is the largest registered owner, with 100.0%.

What is the revenue of MIN-TAKST AS?

MIN-TAKST AS had revenue of NOK −1.8m in 2025.

Who is the general manager of MIN-TAKST AS?

Tore Haugstulen is registered as general manager of MIN-TAKST AS.

Where is MIN-TAKST AS based?

MIN-TAKST AS has its business address in Gjerdrum.

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.