BIZTRAC BETA
Uoppgitt

TRESSVIKA AS

Org. no. 924719117 Limited company (AS) Bømlo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 2.3m
Equity NOK −2.5m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,5 mill kr).

TRESSVIKA AS is registered as a limited company in Bømlo, Vestland with organisation number 924719117. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 2.3m
Equity
NOK −2.5m
Est. value
NOK 11.4m

Financial health · 2024

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

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

Who owns TRESSVIKA AS?

EMMA LØKLING
TRESSVIKA AS
NOK 4.5m rev. · NOK 2.3m profit

TRESSVIKA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRESSVIKA AS

Who owns TRESSVIKA AS?

EMMA LØKLING is the largest registered owner, with 33.3%.

What is the revenue of TRESSVIKA AS?

TRESSVIKA AS had revenue of NOK 4.5m in 2024.

Who is the general manager of TRESSVIKA AS?

Rolf Jostein Grindheim is registered as general manager of TRESSVIKA AS.

Where is TRESSVIKA AS based?

TRESSVIKA AS has its business address in Finnås.

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.