BIZTRAC BETA
Other specialised construction activities n.e.c.

TRANSPORT OG GULVSTØP AS

Org. no. 983554466 Limited company (AS) Bjørnafjorden Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 11.7m
Operating profit NOK 52,000
Equity NOK 3.1m
Incorporated 2001
Employees 5
Share capital NOK 30,000

TRANSPORT OG GULVSTØP AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 983554466. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2001 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 170 shares. The company's stated purpose is: “Transport og gulvstøp, og det som naturlig er i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.7m in revenue and NOK 52,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.7m
Operating profit
NOK 52,000
Equity
NOK 3.1m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns TRANSPORT OG GULVSTØP AS?

ANNE SIRI VIVÅS
TRANSPORT OG GULVSTØP AS
NOK 11.7m rev. · NOK 52,000 profit

TRANSPORT OG GULVSTØP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRANSPORT OG GULVSTØP AS

Who owns TRANSPORT OG GULVSTØP AS?

ANNE SIRI VIVÅS is the largest registered owner, with 100.0%.

What is the revenue of TRANSPORT OG GULVSTØP AS?

TRANSPORT OG GULVSTØP AS had revenue of NOK 11.7m in 2024.

Who is the general manager of TRANSPORT OG GULVSTØP AS?

Anne Siri Vivås is registered as general manager of TRANSPORT OG GULVSTØP AS.

Where is TRANSPORT OG GULVSTØP AS based?

TRANSPORT OG GULVSTØP AS has its business address in Os.

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.