BIZTRAC BETA
Construction of residential and non-residential buildings

RUNE ULRIKSEN AS

Org. no. 998581842 Limited company (AS) Tromsø Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 190,000
Operating profit NOK −153,000
Equity NOK 940,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−153k kr).

RUNE ULRIKSEN AS is registered as a limited company in Tromsø, Troms with organisation number 998581842. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med bygg - og anleggsvirksomhet, og alt som for øvrig står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 190,000 in revenue and NOK −153,000 in operating profit.

Key figures · 2025

Revenue
NOK 190,000
Operating profit
NOK −153,000
Equity
NOK 940,000
Est. value
NOK 471,000

Financial health · 2025

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

Who owns RUNE ULRIKSEN AS?

RUNE ULRIKSEN
RUNE ULRIKSEN AS
NOK 190,000 rev. · NOK −153,000 profit

RUNE ULRIKSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUNE ULRIKSEN AS

Who owns RUNE ULRIKSEN AS?

RUNE ULRIKSEN is the largest registered owner, with 100.0%.

What is the revenue of RUNE ULRIKSEN AS?

RUNE ULRIKSEN AS had revenue of NOK 190,000 in 2025.

Who is the general manager of RUNE ULRIKSEN AS?

Rune Ulriksen is registered as general manager of RUNE ULRIKSEN AS.

Where is RUNE ULRIKSEN AS based?

RUNE ULRIKSEN AS has its business address in Tromsdalen.

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.