BIZTRAC BETA
Civil engineering activities

TVINDE CONSULT AS

Org. no. 835610012 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 2.9m
Equity NOK 70,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-10 Adresseendring registrert 2026-03-10.

TVINDE CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 835610012. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Prosjektledelse & konsulentvirksomhet. Investeringer i eiendom, fond, aksjer samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 2.9m
Equity
NOK 70,000
Est. value
NOK 8.8m

Financial health · 2025

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

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

Who owns TVINDE CONSULT AS?

OLA LØDRUP FOSSUM TVINDE
TVINDE CONSULT AS
NOK 3.4m rev. · NOK 2.9m profit

TVINDE CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TVINDE CONSULT AS

Who owns TVINDE CONSULT AS?

OLA LØDRUP FOSSUM TVINDE is the largest registered owner, with 100.0%.

What is the revenue of TVINDE CONSULT AS?

TVINDE CONSULT AS had revenue of NOK 3.4m in 2025.

Who is the general manager of TVINDE CONSULT AS?

Ola Lødrup Fossum Tvinde is registered as general manager of TVINDE CONSULT AS.

Where is TVINDE CONSULT AS based?

TVINDE CONSULT AS has its business address in Oslo.

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.