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

STEINSVIK TAKST AS

Org. no. 935105595 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 31,000
Incorporated 2025
Share capital NOK 31,000

STEINSVIK TAKST AS is registered as a limited company in Bergen, Vestland with organisation number 935105595. 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 31,000, divided into 31000 shares. The company's stated purpose is: “Takstfirma med tjenester innenfor verditakst og tilstandsrapporter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 31,000
Est. value
NOK 28,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STEINSVIK TAKST AS?

STEINSVIK TAKST AS
NOK 0 rev. · NOK 0 profit

STEINSVIK TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEINSVIK TAKST AS

Who owns STEINSVIK TAKST AS?

Mathias Steinsvik is the largest registered owner, with 100.0%.

What is the revenue of STEINSVIK TAKST AS?

STEINSVIK TAKST AS had revenue of NOK 0 in 2025.

Who is the general manager of STEINSVIK TAKST AS?

Mathias Steinsvik is registered as general manager of STEINSVIK TAKST AS.

Where is STEINSVIK TAKST AS based?

STEINSVIK TAKST AS has its business address in Laksevåg.

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.