BIZTRAC BETA
Rental and operating of own or leased real estate

RUNE TEIG AS

Org. no. 835873242 Limited company (AS) Indre Østfold Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 118,000
Equity NOK 15.4m
Incorporated 1982
Share capital NOK 200,000

RUNE TEIG AS is registered as a limited company in Indre Østfold, Østfold with organisation number 835873242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 200,000. The company's stated purpose is: “Handel, transport, utleie, eiendomsutvikling, investering i verdipapirer og fast eiendom, utleie av arbeidskraft, samt alt som hører naturlig til disse områdene.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 118,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 118,000
Equity
NOK 15.4m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns RUNE TEIG AS?

ATLE NEDBU TEIG
RUNE TEIG AS
NOK 1.9m rev. · NOK 118,000 profit

RUNE TEIG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RUNE TEIG AS own?

RUNE TEIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RUNE TEIG AS

Who owns RUNE TEIG AS?

ATLE NEDBU TEIG is the largest registered owner, with 40.0%.

What is the revenue of RUNE TEIG AS?

RUNE TEIG AS had revenue of NOK 1.9m in 2025.

Who is the general manager of RUNE TEIG AS?

Rune Jostein Teig is registered as general manager of RUNE TEIG AS.

Where is RUNE TEIG AS based?

RUNE TEIG AS has its business address in Askim.

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.